Security Procedures: Ensuring Consistent Execution of Security Requirements
CISM · Information Security Program · Bởi Super Admin
Learn how security procedures provide mandatory, step-by-step processes for achieving security objectives, with examples from Visa's incident response requirements.
The Role of Procedures in a Security Framework
Procedures are detailed, step-by-step processes that individuals and organizations must follow in specific circumstances. Similar to checklists, procedures ensure a consistent process for achieving a security objective. Compliance with procedures is mandatory, distinguishing them from guidelines, which are optional. Organizations may create procedures for building new systems, releasing code to production environments, responding to security incidents, and many other tasks. The mandatory nature of procedures is what makes them effective tools for ensuring that critical security activities are performed consistently and completely.
Procedures occupy a specific place in the policy framework hierarchy. While policies set broad objectives and standards define specific requirements, procedures translate those requirements into concrete, sequential actions. This means that a well-constructed procedure leaves little room for interpretation — it specifies exactly what actions must be taken, by whom, and within what timeframe.
Visa's Incident Response Procedure as a Real-World Example
Visa publishes a document titled "What to Do if Compromised" that lays out a mandatory process that merchants suspecting a credit card compromise must follow. Although the document does not contain the word "procedure" in the title, the introduction clearly states that the document "establishes procedures and timelines for reporting and responding to a suspected or confirmed Compromise Event." The document provides requirements covering several areas of incident response, including notifying Visa of the incident within three days, providing Visa with an initial investigation report, providing notice to other relevant parties, providing exposed payment account data to Visa, conducting a PCI forensic investigation, conducting an independent investigation, and preserving evidence.
Each of these sections provides detailed information on how Visa expects merchants to handle incident response activities. For example, the forensic investigation section describes the use of Payment Card Industry Forensic Investigators (PFI) and specifies that an entity must engage a PFI within five business days, provide Visa with an initial forensic report within ten business days from when the PFI is engaged, and provide Visa with a final forensic report within ten business days of the completion of the review. There is not much room for interpretation in this type of language — Visa is laying out a clear and mandatory procedure describing what actions the merchant must take, the type of investigator they should hire, and the timeline for completing different milestones.
Common Types of Organizational Procedures
Cybersecurity teams commonly include several types of procedures in their policy frameworks. Monitoring procedures describe how the organization will perform security monitoring activities, including the possible use of continuous monitoring technology. Evidence production procedures describe how the organization will respond to subpoenas, court orders, and other legitimate requests to produce digital evidence. Patching procedures describe the frequency and process of applying patches to applications and systems under the organization's care.
Of course, cybersecurity teams may decide to include many other types of procedures in their frameworks, as dictated by the organization's operational needs. The key characteristic shared by all procedures is that they provide a consistent, repeatable process that removes ambiguity from the execution of security requirements. This consistency is what makes procedures a critical component of any mature information security program.
Key takeaways
- Procedures are detailed, step-by-step processes that individuals and organizations must follow, and compliance is mandatory.
- Visa's incident response procedure specifies that merchants must engage a PFI within five business days and provide an initial forensic report within ten business days.
- Common organizational procedures include monitoring procedures, evidence production procedures, and patching procedures.
Thảo luận / Bình luận (0)
Chưa có thảo luận nào cho bài viết này. Hãy gửi bình luận đầu tiên nhé!
Vui lòng Đăng nhập để tham gia thảo luận.