SOLICITATION NOTICE
58 -- IT21 FLEET NOC ANTI SPAM SOFTWARE
- Notice Date
- 12/14/2006
- Notice Type
- Solicitation Notice
- NAICS
- 518111
— Internet Service Providers
- Contracting Office
- P.O. Box 190022, North Charleston SC 29419-9022
- ZIP Code
- 29419-9022
- Solicitation Number
- N65236-07-Q-0142
- Response Due
- 12/19/2006
- Archive Date
- 1/18/2007
- Small Business Set-Aside
- N/A
- Description
- SPAWAR Charleston is seeking quotes for Roaring Penguin AntiSpam Software. This effort shall consist of: 1.1 Hardware Requirements 1.1.1 Must be installed on current and future DNSMAIL servers at the IT- 21 FLTNOC 1.2 Functional Requirements 1.2.1 Must have the ability to filter/pass email through white/black lists 1.2.2 Must have the ability to handle 150% of current estimated traffic burst ceiling (300,000 messages/hour) for entire enterprise 1.2.3 Must have the ability to apply rules such as filtering levels and white/black lists per domain and/or user. There should be a web-based user interface for management. Filtering capabilities should include keyword search, header analysis, message format analysis, Bayesian statistical analysis,blacklists, whitelists, greylists, open proxy lists, Domain Name Service (DNS) verification, Sender Policy Framework (SPF) There should also be spam threshold settings per domain and/or user. The solution should also provide reporting with filtering. 1.3 Software Requirements 1.3.1 Must be compatable with RedHat Enterprise Linux 3.1 and higher 1.3.2 Must be compatable with Perl version 5.6 and higher 1.3.3 Must be compatable with Apache Web Server with Hypertext Preprocessor (PHP) version 4 and higher 1.3.4 Must be compatable with Sendmail version 8.12.x and higher 1.3.5 Must have Anti Virus functionality 1.3.6 Must be a different Anti-Virus vendor than currently fielded Anti Virus solution(s) to provide defense in depth 2.0 QUALIFICATION PROVISIONS The qualification methods that will be used to ensure that the requirements have been met are documented below: The qualification methods that will be used to ensure that the requirements have been met are documented below. A ? Analysis ? A quantitative evaluation of a complete system and/or subsystems by review/analysis of collected data to comply with the specified requirement. D ? Demonstration ? The operation of the system, or a part of the system, that relies on an observable functional operation not requiring the use of instrumentation, special test equipment, or subsequent analysis. I ? Inspection ? The visual examination of system components, documentation, etc. to verify specified requirement has been met. T ? Test ? A measurement or actual operation of the system to prove or show that the product complies with the specified requirement The corresponding letters A, D, I, and T will be shown in the table below, to indicate which method of qualification shall be used for each requirement. Table ?4 1 Requirements Qualification Number Requirement Qualification/Verification Method 3.1.1 Must be installed on hardware that is currently deployed at the IT- 21 FLTNOC at the time of installation I 3.2.1 Must have the ability to filter/pass email through white/black lists D,T 3.2.2 Must have the ability to handle 150% of current estimated traffic burst ceiling (300,000 messages/hour) for entire enterprise. A,D,T 3.2.3 Must have the ability to apply rules per domain and per user A,T 3.3.1 Must be installed on the Linux Operating System RedHat Enterprise 3.1 or higher I 3.3.2 Must have Perl vesion 5.6 or higher installed I 3.3.3 Must have Apache Web Server with PHP version 4 or higher installed I 3.3.4 Must have Sendmail version 8.12.x or higher installed I 3.3.5 Must have Anti Virus functionality I 3.3.6 Must be a different Anti-Virus vendor than currently fielded Anti Virus solution(s) to provide defense in depth I 3.0 REQUIREMENTS TRACEABILITY The sources for each requirement are listed below. The documents used for reference are listed in Section ?2.0. Table ?5 1 Requirements Traceability Requirement Description Source of Requirement 3.1.1 Must be installed on hardware that is currently deployed at the IT- 21 FLTNOC at the time of installation Budgetary Constraints 3.2.1. Must have the ability to filter/pass email through white/black lists NMCI to IT-21 Boundary Baseline Policy 3.2.2 Must have the ability to handle 150% of current estimated traffic burst ceiling (300,000 messages/hour) for entire enterprise Generally accepted industry best practice for mail server capacity planning 3.2.3 Must have the ability to apply rules per domain and per user TSw-SECP-06-0010 3.3.1 Must be installed on the Linux Operating System RedHat Enterprise 3.1 or higher N2N SDD section 3.1.6 Current fielded configuration 3.3.2 Must have Perl vesion 5.6 or higher installed N2N SDD section 3.1.6 Current fielded configuration 3.3.3 Must have Apache Web Server with PHP version 4 or higher installed N2N SDD section 3.1.6 Current fielded configuration 3.3.4 Must have Sendmail version 8.12.x or higher installed N2N SDD section 3.1.6 Current fielded configuration 3.3.5 Must have Anti Virus functionality 5TSW CDD KPP #7 Survivability TSW CDD Attributes 6.2.17 Information Integrity TSW CDD Attributes 6.2.18 Information Integrity Survivability TSW CDD Attributes 6.2.19 Information Integrity and Control TSW CDD Attributes 6.2.20 Confidential Services TSW CDD Attributes 6.2.22 Prevent an Opportunity to Attack 3.3.6 Must be a different Anti-Virus vendor than currently fielded Anti Virus solution(s) to provide defense in depth 5TSW CDD KPP #7 Survivability TSW CDD Attributes 6.2.17 Information Integrity TSW CDD Attributes 6.2.18 Information Integrity Survivability TSW CDD Attributes 6.2.19 Information Integrity and Control TSW CDD Attributes 6.2.20 Confidential Services TSW CDD Attributes 6.2.22 Prevent an Opportunity to Attack CJCSI 6510.01D, DoD Defence in Depth Standard 4.0 NOTES 4.1 Abbreviations Acronym Description DNS Domain Name Service FLTNOC Fleet Network Operations Center IP Internet Protocol IT-21 Information Technology for the 21st Century LANT Atlantic N2N NOC-to-NOC NCTAMS Naval Computer and Telecommunication Area Master Station NOC Network Operations Center PHP Hypertext Preprocessor PAC Pacific SECP Shore Engineering Change Proposal SDD System/Subsystem Design Description SPF Sender Policy Framework TSw Tactical Switching
- Web Link
-
Click on this link to access the SPAWAR Solicitation Page
(https://e-commerce.spawar.navy.mil/Command/02/ACQ/navhome.nsf/homepage?readform&db=navbusopor.nsf&whichdoc=BFA2D5A842F4A62488257244006F0D2C&editflag=0)
- Record
- SN01196870-W 20061216/061214221234 (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 |