DS5.8:

From HORSE - Holistic Operational Readiness Security Evaluation.
Revision as of 19:02, 4 May 2006 by Tdspain (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

DS 5.8 Cryptographic Key Management

Control Objective:

Determine that policies and procedures are in place to organize the generation, change, revocation, destruction, distribution, certification, storage, entry, use and archiving of cryptographic keys to ensure the protection of keys against modification and unauthorized disclosure.

Applicability:

Sarbanes-Oxley
HIPAA
GLBA
PCI
FISMA
NIST SP 800-66
Ditscap
Control Exception
User Defined


Risk Association Control Activities:

1. PCI-3.5.1 Restrict access to keys to the fewest number of custodians necessary.


2. PCI-3.5.2 Store keys securely in the fewest possible locations and forms.


3. PCI-3.6.1 Generation of strong keys.


4. PCI-3.6.2 Secure key distribution.


5. PCI-3.6.3 Secure key storage.


6. PCI-3.6.4 Periodic key changes.


7. PCI-3.6.5 Destruction of old keys.


8. PCI-3.6.6 Split knowledge and dual control of keys (so that it requires 2 or 3 people, each knowing only their part of the key, to reconstruct the whole key).


9. PCI-3.6.7 Prevention of unauthorized substitution of keys.


10. PCI-3.6.8 Replacement of known or suspected compromised keys.


11. PCI-3.6.9 Revocation of old or invalid keys (mainly for RSA keys).


12. PCI-3.6.10 Requirement for key custodians to sign a form specifying that they understand and accept their key-custodian responsibilities.


Implementation Guide:

Process Narrative
Insert a description of the process narration that is applicable to the existing control statement this narrative refers to.

Process Illustration
Insert a process diagram, flowchart or other visual representation here to illustrate the process narrative.

File:Someimage.jpg

Control Commentary
Insert a description of the control that is applicable to the existing control statement this commentary refers to.

Control Exception Commentary
Insert a description of the control exception that is applicable to the existing control statement this commentary refers to.

Evidence Archive Location
Insert Evidence Description Here.

Control Status and Auditors Commentary
Describe the condition of the applicable control and its effectiveness. Set the color icon to a redlock.jpg, yellowlock.jpg or greenlock.jpg.

File:Redlock.jpg

Remediation Plan
Insert remediation plan, applicability, or any information that indicates what needs to be done.

Supplemental Information:
ITIL Security Management
ITIL Security Management Measures
ITIL 4.2 Implementation

ISO 10.3 Cryptographic controls