Please Note: While we have attempted to categorize security requirements for ease of understanding and reading clarity, there are overlapping areas on the matrix in which the same requirements are restated in a slightly different context.
ADMINISTRATIVE PROCEDURES TO GUARD DATA INTEGRITY, CONFIDENTIALITY, AND AVAILABILITY |
||
|
REQUIREMENT: |
IMPLEMENTATION: |
MAPPED STANDARDS: |
|
Certification |
47 |
|
|
Chain of trust partner agreement |
12, 47 |
|
|
Contingency plan (all listed implementation features must be implemented). |
Applications and data criticality analysis |
17, 47, 53 |
|
Data backup plan |
12, 17, 47 |
|
|
Disaster recovery plan |
12, 17, 47, 53 |
|
|
Emergency mode operation plan |
47, 53 |
|
|
Testing and revision |
12, 17, 47 |
|
|
Formal mechanism for processing records |
12, 17 |
|
|
Information access control (all listed implementation features must be implemented). |
Access authorization |
12, 17, 47, 53 |
|
Access establishment |
17, 47, 53 |
|
|
Access modification |
12, 17, 47, 53 |
|
|
Internal audit |
12, 17, 43, 44, 47 |
|
|
Personnel security (all listed implementation features must be implemented) |
Assure supervision of maintenance personnel by authorized, knowledgeable person |
17, 47 |
|
Maintainance of record of access authorizations |
12, 17, 47 |
|
|
Operating, and in some cases, maintenance personnel have proper access authorization |
17, 47 |
|
|
Personnel security policy/procedure |
17, 47, 53 |
|
|
System users, including maintenance personnel, trained in security |
12, 17, 47, 53 |
|
|
Security configuration mgmt. (all listed implementation features must be implemented). |
Documentation |
12, 17, 47, 53 |
|
Hardware/software installation & maintenance review and testing for security features |
12, 17, 47 |
|
|
Inventory |
12, 17 |
|
|
Security testing |
12, 17, 47 |
|
|
Virus checking |
12, 17, 47, 53 |
|
|
Security incident procedures (all listed implementation features must be implemented). |
Report procedures |
12, 17, 47 |
|
Response procedures |
17, 47 |
|
|
Security management process (all listed implementation features must be implemented). |
Risk analysis |
12, 17, 47, 53 |
|
Risk management |
17, 47 |
|
|
Sanction policy |
12, 17, 47, 53 |
|
|
Security policy |
17, 47, 53 |
|
|
Termination procedures (all listed implementation features must be implemented). |
Combination locks changed |
12, 17 |
|
Removal from access lists |
12, 17, 47, 53 |
|
|
Removal of user account(s) |
12, 17, 47 |
|
|
Turn in keys, token or cards that allow access |
12, 17, 47 |
|
|
Training (all listed implementation features must be implemented). |
Awareness training for all personnel (including mgmt). |
12, 17, 18, 47, 53 |
|
Periodic security reminders |
12, 18 |
|
|
User education concerning virus protection |
||
|
User education in importance of monitoring log in success/failure, and how to report discrepancies |
12, 17, 18 |
|
|
User education in password management |
12, 18, 47 |
|
PHYSICAL SAFEGUARDS TO GUARD DATA INTEGRITY, CONFIDENTIALITY, AND AVAILABILITY |
||
|
REQUIREMENT: |
IMPLEMENTATION: |
MAPPED STANDARDS: |
|
Assigned security responsibility |
47 |
|
|
Media controls (all listed implementation features must be implemented). |
Access control |
17, 47, 53 |
|
Accountability (tracking mechanism) |
17, 18, 47 |
|
|
Data backup |
12, 17, 47, 53 |
|
|
Data storage |
12, 17, 47 |
|
|
Disposal |
17, 47, 53 |
|
|
Physical access controls (limited access) (all listed implementation features must be implemented). |
Disaster recovery |
17 |
|
Emergency mode operation |
17 |
|
|
Equipment control (into and out of site) |
17, 47 |
|
|
Facility security plan |
12, 17, 47 |
|
|
Procedures for verifying access authorizations prior to physical access |
17, 18, 47 |
|
|
Maintenance records |
17 |
|
|
Need-to-know procedures for personnel access |
12, 17, 47, 53 |
|
|
Sign-in for visitors and escort, if appropriate |
17 |
|
|
Testing and revision |
17, 47 |
|
|
Policy/guideline on work station use |
18 |
|
|
Secure work station location |
17, 53 |
|
|
Security awareness training |
12, 17, 47 |
|
TECHNICAL SECURITY SERVICES TO GUARD DATA INTEGRITY, CONFIDENTIALITY, AND AVAILABILITY |
||
|
REQUIREMENT: |
IMPLEMENTATION: |
MAPPED STANDARDS: |
|
Access control (The following implementation feature must be implemented: Procedure for emergency access, In addition, at least one of the following three implementatin features must be implemented : Context-based access, Role-based access, User-based access. The use of Encryption is optional). |
Context-based access |
5, 12, 14, 16, 17, 40, 47 |
|
Encryption |
1, 6, 12, 14, 17, 21, 22, 23, 24, 26, 36, 28, 29, 30, 31, 47, 49, 53, 54, 55 |
|
|
Procedure for emergency access |
14, 17, 53 |
|
|
Role-based access |
14, 16, 17, 40, 41, 47, 53 |
|
|
User-based access |
11, 12, 14, 16, 17, 40, 41, 47, 53 |
|
|
Audit controls |
12, 14, 18, 47, 53 |
|
|
Authorization control (At least one of the listed implementation features must be implemented). |
Role-based access |
5, 14, 16, 17, 47, 53 |
|
User-based access |
14, 16, 47, 53 |
|
|
Data authentication |
11, 53 |
|
|
Entity Authentication (The following implementation features must be implemented: Automatic logoff, Unique user identification. In addition, at least one of the other listed implementation features must be implemented). |
Automatic logoff |
14, 16, 17, 18, 40, 53 |
|
Biometric |
14, 16, 18, 40, 47, 53 |
|
|
Password |
14, 16, 17, 18, 19, 40, 47, 53 |
|
|
PIN |
14, 16, 18, 19, 40, 47 |
|
|
Telephone callback |
14, 17, 18, 47, 53 |
|
|
Token |
14, 17, 47, 50, 53 |
|
|
Unique user identification |
14, 47, 53 |
|
TECHNICAL SECURITY MECHANISMS TO GUARD DATA INTEGRITY, CONFIDENTIALITY, AND AVAILABILITY |
||
|
REQUIREMENT: |
IMPLEMENTATION: |
MAPPED STANDARDS: |
|
Communications/network controls (If communications or networking is employed, the following implementation features must be implemented: Integrity controls, Message authentication. In addition, one of the following implementation features must be implemented: Access controls, Encryption. In addition, if using a network, the following four implementation features must be implemented: Alarm, Audit trail, Entity authentication, Event reporting). |
Access controls |
14, 17, 22, 23, 39, 47, 48, 53 |
|
Alarm, event reporting, and audit trail |
14, 17, 18, 35, 36, 37, 38, 44 |
|
|
Audit trail |
||
|
Encryption |
1, 6, 12, 14, 17, 21, 22, 23, 24, 26, 27, 28, 29, 30, 31, 47, 49, 52, 53 |
|
|
Entity authentication |
12, 14, 17, 18, 20, 22, 23, 31, 32, 34, 33, 51, 53 |
|
|
Event reporting |
||
|
Integrity controls |
14, 15, 17, 18, 22, 23, 45, 46 |
|
|
Message authentication |
14, 15, 17, 18, 22, 23, 25, 45, 46, 52 |
|
ELECTRONIC SIGNATURE |
||
|
REQUIREMENT: |
IMPLEMENTATION: |
MAPPED STANDARDS: |
|
Digital signature (If digital signature is employed, the following three implementation features must be implemented: Message integrity, Non-repudiation, User authentication. Other implementation features are optional). |
Ability to add attributes |
3, 4, 10, 11, 13, 20 |
|
Continuity of signature capability |
3, 4, 11, 13, 14, 18 |
|
|
Counter signatures |
3, 4, 10, 11, 13, 14, 18 |
|
|
Independent verifiability |
3, 4, 11, 13, 20 |
|
|
Interoperability |
3, 4, 7, 8, 9, 13, 14, 48 |
|
|
Message integrity |
3, 4, 10, 11, 13, 14, 18 |
|
|
Multiple signatures |
3, 4, 10, 11, 13, 20 |
|
|
Non-repudiation |
2, 3, 4, 10, 11, 13, 14, 42, |
|
|
Transportability |
3, 4, 11, 13, 14, 18 |
|
|
User authentication |
3, 4, 10, 11, 13, 20 |
|
[FR Doc. 98-21601 Filed 8-7-98; 1:23 p.m.]
BILLING CODE 4120-01-P