SOURCES SOUGHT
70 -- Audit Server Request for Information
- Notice Date
- 4/18/2005
- Notice Type
- Sources Sought
- NAICS
- 511210
— Software Publishers
- Contracting Office
- Defense Information Systems Agency, Procurement and Logistics, DITCO-NCR, P.O. 4502, Arlington, VA, 22204-4502
- ZIP Code
- 22204-4502
- Solicitation Number
- Reference-Number-CRRFI41805
- Response Due
- 5/15/2005
- Archive Date
- 5/15/2005
- Description
- THIS IS A REQUEST FOR INFORMATION (RFI) AND NOT A REQUEST FOR PROPOSAL (RFP) The Defense Information Systems Agency (DISA) is seeking sources that are capable of providing a commercial product suite for a Department of Defense (DOD) enterprise-wide, distributed architecture for auditing security logs from a variety of computer architectures and operating systems. The software must be capable of identifying and evaluating events, and providing alerts to a user community based upon configurable site rules. The system will reside on the Unclassified but Sensitive Internet Protocol Router Network (NIPRNet) and Secret Internet Protocol Router Network (SIPRNet), and will utilize Virtual Private Network (VPN), Local Area Network (LAN) and Wide Area Network (WAN) technologies. The IT environments in which auditing will occur may be any or all of the following: Unclassified, Confidential, Secret and Top Secret. The audit server software must collect from a variety of operating systems, application software, databases and communication devices such as firewalls and routers. The audit server software must be capable of auditing itself internally. Transmission methods should utilize mechanisms to maintain the security and integrity of the data. This includes but is not limited to: compression, hash counts, encryption, and secure layering of transmission. For alerting purposes and to preclude tampering, the transmission must be timely. The transmission architecture must be able to send and receive data in streaming mode and in failsafe batch-processing mode in the event of network issues. Users must be able to scan the database locally and remotely. Users must be able to review their records, however they should be prevented from reviewing data belonging to other projects. The user view must incorporate a graphical user interface (GUI) that displays multiple levels of alerting for easier identification and notification of log events. The GUI-interface should not reside on the same system as the audit server database. The GUI should provide users and administrators with easy access to their data and to the control clients. The GUI should provide real-time policy control and alerting capabilities. Data should be stored on-line for a minimum of one week, to provide users ample time to review records in the database and possibly use records as a reference should an incursion occur. Off-line storage of the binary data and audit logs for a period of at least one year is required. For legal proceedings in the event of a security breach, data may be required to be retrievable for periods longer than one year. The audit server must have the ability to retrieve and parse stored binary files at any time for analysis. To preclude tampering with the audit data once it has been collected, the audit server database should log all events internally within the repository server application. Events and triggers should be capable of being dynamically configured to inform of potential situations. The vendor will be responsible for providing version upgrades, releases and patches. Software must have applied for and received a National Information Assurance Partnership (NIAP) conformance claim rating of EAL4 or have applied for and will receive their rating for the product within one calendar year. There is no bid package or solicitation document associated with this announcement. The requested information is for planning purposes and does not constitute a commitment, implied or otherwise, that a procurement action will be issued. No entitlement to payment of direct or indirect costs or charges by the Government will arise as the result of the submission of contractor's information. The Government shall not be liable for or suffer any consequential damages for proprietary information not properly identified. Proprietary information will be safeguarded in accordance with the applicable Government regulations. Interested firms should email their capability statement addressing the above requirement to Mr. Steve Yogodzinski at Steve.Yogodzinski@disa.mil by 15 May 2005. Firms should also provide their business size, CAGE Code, DUNS number, and GSA Schedule contract number, if applicable.
- Record
- SN00790027-W 20050420/050418211525 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |