SOURCES SOUGHT
70 -- PPPL Network Access Control System
- Notice Date
- 9/5/2008
- Notice Type
- Sources Sought
- NAICS
- 511210
— Software Publishers
- Contracting Office
- Department of Energy, Princeton Plasma Physics Laboratory (DOE Contractor), Princeton University, US Route 1 North at Sayre Drive, P.O. Box CN-17, Princeton, New Jersey, 08543
- ZIP Code
- 08543
- Solicitation Number
- PPPL-08-27-2008
- Response Due
- 9/22/2008
- Archive Date
- 10/7/2008
- Point of Contact
- Rodney D Templon,, Phone: 609-243-2443
- E-Mail Address
-
rtemplon@pppl.gov
- Small Business Set-Aside
- N/A
- Description
- Princeton Plasma Physics Laboratory (PPPL) seeks a commercial Network Access Control (NAC) system with the following salient features: (1) A clear path for migrating from PPPL's existing homegrown NAC solution to the new NAC solution. The existing homegrown solution is based upon MAC address radius authentication. In deploying a new system, it is expected that the vendor will work with PPPL to slowly migrate to the new system as well as gradually introduce its features. (2) Ability to work with existing PPPL network hardware. An acceptable NAC solution must be able to integrate with all of PPPL's existing network hardware (primarily Enterasys-based). This includes all existing switches, routers, firewalls, wireless access points, etc. (3) Provision of client endpoint inspection/remediation in both a client and clientless fashion prior to connection to PPPL's network. PPPL operates in a mixed environment and thus will require a solution that is able to interrogate several different platforms. For Windows (2000, XP, and Vista), Macintosh (OS X on both the PPC and Intel architectures), and Linux (Red Hat is a must), PPPL requires that agent-based interrogation be available. With agent-based interrogation it is expected that comprehensive and advanced endpoint inspection be possible. PPPL also expects that all endpoint inspection be carried out in a timely fashion such that the delay in obtaining network access is minimal. This functionality should be available for all computers on PPPL's network regardless of whether or not they belong to visitors, other labs, are personally owned, etc. (4) Freedom from any type of network drops and/or outages. PPPL relies heavily on its network to carry out its day-to-day operations. Disruption of any kind to the flow of traffic on the network could result in the loss of critical experimental data and/or productivity. Thus, it is vital that the NAC solution, once fully deployed, be able to handle all traffic on PPPL's network without interruption. (5) A database accessible from other systems. PPPL presently has a homegrown web-reporting tool that is utilized to gather information about all devices on its network. It is essential that the information gathered by the NAC solution be easily appended to these reports. Thus, PPPL requires that the database utilized by the NAC solution be stored in such a manner that the existing MS SQL reporting database can be joined with it. (6) The software must be compatible with 802.1x authentication. While PPPL currently uses MAC based authentication for NAC, it is desirable to switch to 802.1x. It is thus essential that any NAC solution introduced into the PPPL environment be capable of 802.1x authentication. (7) The NAC solution must be flexible enough to work with the large variety of equipment that PPPL utilizes on its network. As an experimental facility, PPPL utilizes a vast array of equipment on its network. This includes but is not limited to laptops, desktops, projectors, pdas, cell phones, and oscilloscopes. (8) The NAC appliance must be able to function properly with our VPN. PPPL currently utilizes a web based SSL VPN. Acceptable NAC solutions will integrate with this system. (9) The offeror must be willing to offer a proof of concept at no cost to PPPL. Before purchasing a NAC solution, PPPL wishes to conduct an evaluation of its performance in the actual operating environment. During the evaluation, PPPL will put the NAC solution through vigorous testing to ensure that it meets all expectations. It is also expected that PPPL will receive technical support from the offeror at no cost during this trial period, should it be required. (10) The NAC solution must be able to perform flexible VLAN assignment. The successful NAC solution will be able to assign an endpoint to a specific VLAN based upon several factors including but not limited to: (a) Any prior contact with PPPL's network; (b) A lack of prior connectivity to PPPL's network; (c) The results of an endpoint inspection; (d) Manually, via a NAC administrator; or (e) The amount of time that has passed since the device was last connected to the network. (11) The NAC solution must give end-users the following capabilities: (a) Allow users to register a new machine on PPPL's network; (b) Issue a computer usage statement to users prior to network registration; and (c) Allow users to renew their endpoint's registration prior to its expiration. (12) The NAC solution must integrate with our existing wireless network. PPPL currently takes advantage of several wireless networks. It is expected that the NAC system be able to integrate with both our unencrypted and WAP encrypted wireless networks. In addition to these above-listed salient features, PPPL has identified two highly desirable features in any selected NAC solution: (1) Prevent MAC address spoofing. With the introduction of a commercial NAC system, PPPL would like to be able to identify MAC address spoofing. Should any type of MAC address spoofing be spotted, it is desirable that PPPL be able to take some sort of action. (2) Authentication to the administrative console should be handled by a directory service This announcement is not a solicitation and does not obligate PPPL to issue a solicitation. Interested parties who feel that they can provide a NAC solution with the twelve salient features described above should submit a capability statement demonstrating their capacity to perform this workscope. Information submitted should describe your organization, personnel, proposed software product(s), applicable subcontractor network and past experience to meet specific needs stated above. Include company name, address, telephone number, technical point of contact, software nomenclature, description, and brochure/literature. Please ensure that the information offered adequately addresses each of the twelve (12) salient features and two (2) highly desirable features set forth above. As indicated above, to assist in demonstrating the ability of the recommended software to operate successfully in PPPL's environment, PPPL desires offers for risk-free, closed-end trial installations of the offeror's recommended software under the following conditions: (1) The installation must include installation support, user support, and de-installation support, and be fully cost-free to PPPL; (2) the offeror must agree that PPPL will incur no liability of any kind by its use of the supplied software and media; and (3) the offeror must agree that PPPL's trial use of the software does not create an obligation to purchase software or services of any kind from the performing offeror. Please send your responses to Rodney D. Templon at the office identified above, by fax to (609) 243-2021 or by email to rtemplon@pppl.gov. Electronic submittals are preferred. To be considered by PPPL, documentation should be received within fifteen (15) days after the date of publication of this synopsis. Please be advised that PPPL will not pay for any information submitted in response to this announcement.
- Web Link
-
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=a86f3c76503e70a7bc17697c307ef99e&tab=core&_cview=1)
- Place of Performance
- Address: Princeton Plasma Physics Laboratory, James Forrestal Campus, U.S. Route 1 North at Sayre Drive, Princeton, New Jersey, 08543, United States
- Zip Code: 08543
- Zip Code: 08543
- Record
- SN01661445-W 20080907/080905222753-a86f3c76503e70a7bc17697c307ef99e (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |