FIPS compliance
Under the Information Technology Management Reform Act (Public Law 104-106), the Secretary of Commerce approves standards and guidelines that are developed by the National Institute of Standards and Technology (NIST) for Federal computer systems. These standards and guidelines are issued by NIST as Federal Information Processing Standards (FIPS) for use government-wide. NIST develops FIPS when there are compelling Federal government requirements such as for security and interoperability and there are no acceptable industry standards or solutions.
FIPS mode is supported on local, and remote SmartConnectors.
Note: When FIPS-compliant connectors connect to a non-FIPS-compliant destination, the solution is not considered FIPS compliant. Also, when the destination is installed in FIPS Suite B compliant mode, the SmartConnectors also must be installed in FIPS Suite B compliant mode.
FIPS Suite B
FIPS Suite B includes cryptographic algorithms for hashing, digital signatures, and key exchange. The entire suite of cryptographic algorithms is intended to protect both classified and unclassified national security systems and information.
FIPS compliant Connectors
The following connectors are FIPS compliant:
-
All syslog connectors
-
All file reader connectors
-
All SNMP connectors
-
Most database connectors (except Oracle Audit DB and when using SQL Server drivers with encryption)
-
Cisco Secure IPS SDEE connectors
-
Sourcefire Defense Center eStreamer connector
-
Check Point OPSEC NG connector
FIPS non-compliant SmartConnectors
The following SmartConnectors are not FIPS compliant:
-
Database connectors using SQL Server drivers with encryption
-
Connectors using Oracle drivers
SmartConnectors Not certified as FIPS compliant
The following connectors are not certified as FIPS compliant:
-
API connectors with proprietary internal mechanisms
- Web Services and Cloud connectors