DS5.6:
DS 5.6 Security Incident Definition
Control Objective:
Ensure that the characteristics of potential security incidents are clearly defined and communicated so security incidents can be properly treated by the incident or problem management process. Characteristics include a description of what is considered a security incident and its impact level. A limited number of impact levels are defined and for each the specific actions required and the people who need to be notified are identified.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
- 1. Risk: Security incidents and incompliance with information security procedures may go overlooked and not addressed.
- a. SOX.3.1.1: Management should monitor security incidents and the extent of compliance with information security procedures.
- a. SOX.3.1.1: Management should monitor security incidents and the extent of compliance with information security procedures.
- 1. Risk: Security incidents and incompliance with information security procedures may go overlooked and not addressed.
- PCI-10.3.1 User identification.
- PCI-10.3.2 Type of event.
- PCI-10.3.3 Date and time.
- PCI-10.3.4 Success or failure indication.
- PCI-10.3.5 Origination of event.
- PCI-10.3.6 Identity or name of affected data, system component, or resource.
- PCI-12.9.1 Create an incident response plan to be used in the event of system compromise. Ensure the plan addresses, at a minimum, specific incident response procedures, business recovery and continuity procedures, data backup processes, roles and responsibilities, and communication and contact strategies (e.g., informing Acquirers and credit card associations.).
- PCI-12.9.2 Test the plan at least annually.
- PCI-12.9.3 Designate specific personnel to be available on a 24/7 basis to respond to alerts.
- PCI-12.9.4 Provide appropriate training to staff with security breach response responsibilities.
- PCI-12.9.5 Include alerts from intrusion detection, intrusion prevention, and file integrity monitoring systems.
- PCI-12.9.6 Have a process to modify and evolve the incident response plan according to lessons learned and to incorporate industry developments.
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 and Security Management.
ITIL 3.3.2 Incident control/help desk.
ISO 3.1 Information security policy.
ISO 4.1 Information security infrastructure.
ISO 6.3 Responding to security incidents and malfunctions.
ISO 8.1 Operational procedures and responsibilities.
ISO 9.5 Operating system access control.
Implementation guidance
Insert guidance in this section if it helps to elaborate upon the subject matter. Examples of evidence that would help guide the end user is desirable.