130n@calvinlai.com
  • About Calvin Lai (fkclai)
  • My Work
  • Cyber Security
    • Cyber Security Centre (CSC)
      • Why we need a CSC
      • CSC Team Structure: Roles, Functions, and Tools
        • Key Function & Role
        • Tools & Platforms
        • People
        • Outsource Strategy
      • HRMC Executive Paper
  • Detection and Response
    • Playbook: Threat Prioritization & Automated Response Strategies
      • Scenario: Detecting and Mitigating a Ransomware Attack
      • Scenario: DC Sync Attack Detected and Mitigated
      • Scenario: Pass-the-Hash (PtH) Attack Detected and Contained
      • Scenario: Phishing Campaign with Malware / Credential Theft Detected and Mitigated
  • Application Architecture
    • Comparison of MVC , N-tier and Microservice Architecture
  • Application Security
    • OAuth, SAML, and OpenID Connect: Key Differences and Use Cases
    • Secure Coding Principles
    • HTTP Header Security Principles
    • Mitigating Broken Object Level Authorization (BOLA)
    • Spring Boot Validation
    • Output Encoding in JavaServer Faces (JSF)
    • Session Management Security Issues
    • Common API Security Problems
      • Broken Authentication
      • Excessive Data Exposure
      • Lack of Resources & Rate Limiting
      • Broken Function Level Authorization
      • Unsafe Consumption of APIs
    • JAVA Exception Handling
    • File Upload Validation
    • OAuth 2.0 Security
      • Insecure Storage of Access Tokens
    • Microservice Security
      • Sample Coding Demo
        • Service Implementation
        • Client Interaction
      • Security Solution for Microservices Architecture
    • Modifying and Protecting Java Class Files
      • Modify a Class File Inside a WAR File
      • Direct Bytecode Editing
        • Steps to Directly Edit a Java Class File
          • Update: Java Bytecode Editing Tools
      • Techniques to Protect Java Class Files
        • Runtime Decryption in WebLogic
    • JAVA Program
      • Secure, Concurrent Web Access Using Java and Tor
      • Creating a Maven Java project in Visual Studio Code
  • Exploit/CVE PoC
    • ZeroLogon Exploit
    • Remote Retrieved Chrome saved Encrypted Password
    • Twitter Control an RCE attack
  • Hacking Report (HTB)
    • Hits & Summary
      • Tools & Cheat Sheet
    • Windows Machine
      • Love 10.10.10.239
      • Blackfield 10.10.10.192
      • Remote 10.10.10.180
      • Sauna 10.10.10.175
      • Forest 10.10.10.161
      • Sniper
      • Json
      • Heist
      • Blue
      • Legacy
      • Resolute
      • Cascade
    • Linux Machine
      • Photobomb 10.10.11.182
      • Pandora 10.10.11.136
      • BountyHunter 10.10.11.100
      • CAP 10.10.10.245
      • Spectra 10.10.10.229
      • Ready 10.10.10.220
      • Doctor 10.10.10.209
      • Bucket 10.10.10.212
      • Blunder 10.10.10.191
      • Registry 10.10.10.159
      • Magic
      • Tabby
  • Penetration Testing
    • Web Application PenTest
    • Network/System PenTest
    • Mobile Penetration Test
      • Certificate Pinning
        • Certificate Pinning Bypass (Android)
          • Root a Android Device
          • Setup Proxy Tool - Burp Suite
      • Checklist
  • Threat Intelligence
    • Advanced Persistent Threat (APT) groups
      • North Korean APT Groups
      • Chinese APT Groups
      • Russian APT Groups
      • Other APT
  • Red Team (Windows)
    • 01 Reconnaissance
    • 02 Privileges Escalation
    • 03 Lateral Movement
    • 04 AD Attacks
      • DCSync
    • 05 Bypass-Evasion
    • 06 Kerberos Attack
    • 99 Basic Command
  • Exploitation Guide
    • 01 Reconnaissance
    • 02 Port Enumeration
    • 03 Web Enumeration
    • 04 Windows Enum & Exploit
      • Windows Credential Dumping
        • Credential Dumping: SAM
        • Credential Dumping: DCSync
      • Kerberos Attack
      • RDP
    • 05 File Enumeration
    • 06 Reverse Shell Cheat Sheet
      • Windows Reverse Shell
      • Linux Reverse Shell
    • 07 SQL Injection
    • 08 BruteForce
    • 09 XSS Bypass Checklist
    • 10 Spring Boot
    • 11 WPA
    • 12 Payload list
  • Vuln Hub (Writeup)
    • MrRobot
    • CYBERRY
    • MATRIX 1
    • Node-1
    • DPwwn-1
    • DC7
    • AiWeb-2
    • AiWeb-1
    • BrainPan
  • CTF (Writeup & Tips)
    • CTF Tools & Tips
    • Hacker One
    • CTF Learn
    • P.W.N. University - CTF 2018
    • HITCON
    • Pwnable
      • 01 Start
  • Useful Command/Tools
    • Kali
    • Windows
    • Linux
  • Offensive Security Lab & Exam
    • Lab
    • Tools for an Offensive Certification
      • Strategy for an Offensive Exam Certification
        • CVEs
        • Privilege Escalation
        • Commands
        • Impacket
  • ISO 27001
    • Disclaimer
    • What is ISO 27001
      • Implementation
    • Documentation
    • Common Mistake
    • Q&A
      • Can internal audit to replace the risk assessment
      • Is it sufficient for only the IT department head to support the ISO 27001 program
      • Does the Business Continuity Plan (BCP) and a Disaster Recovery Plan (DRP) are the same?
    • ISO 27001 Controls and Domains
      • 1. Information Security Policies
      • 2. Organization of Information Security
      • 3. Human Resource Security
      • 4. Asset Management
      • 5. Access Control
      • 6. Cryptographic Controls
      • 7. Physical and Environmental Security
      • 8: Operational Security
      • 9. Communications Security
      • 10. System Acquisition, Development, and Maintenance
      • 11. Supplier Relationships
      • 12: Information Security Incident Management
      • 13. Information Security Aspects of Business Continuity Management
      • 14. Compliance
Powered by GitBook
On this page
  • Controls (A.16):
  • Control A.16.1.1: Responsibilities and Procedures
  • Control A.16.1.2: Reporting Information Security Events
  • Control A.16.1.3: Reporting Information Security Weaknesses
  • Control A.16.1.4: Assessment of and Decision on Information Security Events
  • Control A.16.1.5: Response to Information Security Incidents
  • Control A.16.1.6: Learning from Information Security Incidents
  • Control A.16.1.7: Collection of Evidence

Was this helpful?

  1. ISO 27001
  2. ISO 27001 Controls and Domains

12: Information Security Incident Management

This category focuses on ensuring a consistent and effective approach to managing information security incidents, including communication on security events and weaknesses. It involves planning, monitoring, and responding to incidents to minimize adverse impacts and ensure that lessons are learned to prevent future incidents.

Controls (A.16):

  • A.16.1.1: Responsibilities and Procedures

  • A.16.1.2: Reporting Information Security Events

  • A.16.1.3: Reporting Information Security Weaknesses

  • A.16.1.4: Assessment of and Decision on Information Security Events

  • A.16.1.5: Response to Information Security Incidents

  • A.16.1.6: Learning from Information Security Incidents

  • A.16.1.7: Collection of Evidence

Control A.16.1.1: Responsibilities and Procedures

Audit Questions:

  • Are there documented procedures for managing information security incidents?

  • Who is responsible for managing and responding to security incidents?

  • How are these responsibilities communicated?

Common Non-Conformities (NC):

  • Lack of documented incident management procedures.

  • Unclear or undefined responsibilities for incident management.

  • Inadequate communication of incident management responsibilities.

Control A.16.1.2: Reporting Information Security Events

Audit Questions:

  • Are there procedures for reporting information security events?

  • How are security events reported, and to whom?

Common Non-Conformities (NC):

  • No procedures for reporting security events.

  • Delays or failures in reporting security events.

Control A.16.1.3: Reporting Information Security Weaknesses

Audit Questions:

  • How are information security weaknesses reported?

  • Are there channels for employees to report weaknesses confidentially?

Common Non-Conformities (NC):

  • No procedures for reporting security weaknesses.

  • Employees unaware of reporting channels.

Control A.16.1.4: Assessment of and Decision on Information Security Events

Audit Questions:

  • How are security events assessed and decisions made regarding their handling?

  • Are there criteria for assessing the severity of events?

Common Non-Conformities (NC):

  • Inadequate assessment procedures for security events.

  • Lack of criteria for assessing event severity.

Control A.16.1.5: Response to Information Security Incidents

Audit Questions:

  • What are the procedures for responding to information security incidents?

  • How is the effectiveness of incident response measured?

Common Non-Conformities (NC):

  • No response procedures for security incidents.

  • Poor measurement of incident response effectiveness.

Control A.16.1.6: Learning from Information Security Incidents

Audit Questions:

  • Are there processes for learning from information security incidents?

  • How are lessons learned documented and communicated?

Common Non-Conformities (NC):

  • No processes for learning from incidents.

  • Lessons learned not documented or communicated.

Control A.16.1.7: Collection of Evidence

Audit Questions:

  • How is evidence collected and preserved during incident investigation?

  • Are there procedures to ensure evidence integrity?

Common Non-Conformities (NC):

  • Inadequate evidence collection procedures.

  • Lack of measures to ensure evidence integrity.

Previous11. Supplier RelationshipsNext13. Information Security Aspects of Business Continuity Management

Last updated 4 months ago

Was this helpful?