ISO 27001 Annex : 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

In this article explain ISO 27001 Annex : 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 this controls.

A.16.1.5 Response to Information Security Incidents

Control- In the context of the documented procedures, information security incidents should be responded to.

Implementation Guidance- A nominated point of contact and other pertinent people within the organization or external parties should be able to respond to information security incidents.

The following should be included in the response:
  • Gathering evidence as soon as possible after the occurrence;
  • Conduct forensic security information analysis where necessary;
  • Escalation, wherein necessary;
  • Ensuring adequate documentation for subsequent analysis of all responses activities involved;
  • Communicate to other internal or external entities or organizations who need to know if an information security incident occurs or any specific details thereof;
  • Addressing the weaknesses identified for information security or contributing to the incident;
  • The formal closing and recording of the incident until effectively concluded.

The investigation should be performed after the incident to determine the cause of the accident, if appropriate.

Related Product :  ISO 27001 Lead Auditor Training And Certification ISMS

Other information- The first goal of the response to an incident is to restore the ‘daily security level’ and then start the necessary recovery.

A.16.1.6 Learning from Information Security Incidents

Control – To minimize the risk or effect of potential accidents, the experience obtained from the study and mitigation of information security accidents should be used.

Implementation Guidance- Mechanisms will be in place to measure and track the forms, quantities, and costs of events affecting information security. In order to classify recurring or high impact events, the information obtained from the information security events assessment should be used.

Other Information- In order to minimize the occurrence, harm and expense of potential accidents, or take account of the security policy analysis process, assessment of information security accidents that suggest that improved or additional controls are required (refer 5.1.2).

Facts and figures from real events in the security of information can be used in user awareness training with due consideration of confidentiality (refer 7.2.2) as examples of how these events may be handled and how to prevent them in the future.

Also Read : A.16.1.2 , A.16.1.3 & A.16.1.4 

A.16.1.7 Collection of Evidence

Control- The organization will define, obtain, procure and retain information as documentation and implement procedures.

Implementation Guidance- External protocols for treating evidence for administrative and legal action should be established and tracked.

In general, the processes of defining, gathering, acquiring, and preserving the proof should be in line with various media types, technologies, and device specifications e.g. based on or off.

The procedures will take into consideration:
  • Custody chain;
  • Evidence of security
  • Personnel security;
  • The staff’s roles and responsibilities;
  • Personnel competency;
  • Documentation;
  • Briefing.

Certification or all other applicable staff and instrument credentials should be pursued where possible in order to strengthen the validity of the evidence retained.

Forensic findings can extend beyond the boundaries of association or jurisdiction. In these cases, the organization should be given the right to collect the required information as forensic proof. In order to optimize admission opportunities across the qualified jurisdictions, the criteria of the different jurisdictions should also be considered.

Other Information- The quest for, detection and recording of possible evidence requires identification. The collection process is the set of physical objects which may contain potential evidence. The method of acquisition is to create a copy of the data in a given package. Preservation is the mechanism by which probable evidence is stored and preserved.

This may not be clear if the incident would result in legal proceedings unless an information security issue is identified first. The risk, therefore, exists that the required proof may be intentionally or inadvertently lost prior to the seriousness of the incident. Any legal proceedings to be taken and guidance on the facts needed is recommended to involve a lawyer or police at an early age.

The guideline for identifying, collecting, acquiring and preserving digital evidence is provided by ISO / IEC 27037.

A well-known ISO 27001 Lead Auditor and ISO 27001 Lead Implementer certificate that mainly covers information security clauses and their implementation, i.e., controls which should be implemented by the organization to preserve the CIA triad, Confidentiality, Integrity, and Availability to maintain their critical, sensitive information in a secure manner. Infosavvy , an institute in Mumbai conducts training and certification for multiple domains in Information Security which includes IRCA CQI ISO 27001:2013 Lead Auditor (LA), ISO 27001 Lead Implementer (LI) (TÜV SÜD Certification). Infosavvy will help you to understand and recognize the full scope of your organization’s security checks to protect your organization’s activities and information equipment (assets) from attacks, and how to respond to any incident happened violating information security, and the process of defining, gathering, acquiring, and documenting the proof. We have trainers with extensive expertise and experience to ensure the efficient handling of the security of information. Consequently, the applicant will gain the necessary skills for the ISMS audit by using commonly agreed audit concepts, procedures, and techniques.

Questions related to this topic

  1. What is ISO 27001 Annex : A.16.1.5 Response to Information Security Incidents?
  2. What is an example of a security incident?
  3. What are the 114 controls of ISO 27001?
  4. Explain ISO 27001 Annex : A.16.1.5 Response to Information Security Incidents?
  5. How many controls are there in ISO 27001 standard?

ISO 27001 Requirements


Clause 4.4 Information security management system
Clause 4.3 Determining the scope of the information security management system
Clause 5.1 Leadership and commitment
Clause 5.2 Policy
Clause 5.3 Organizational roles, responsibilities and authorities 
Clause 6.1 Actions to address risks and opportunities
Clause 6.1.2 Information security risk assessment process
Clause 6.1.3 Information security risk treatment
Clause 6.2 Information security objectives & planning
Clause 7.1 Resources
Clause 7.2 Competence
Clause 7.3 Awareness
Clause 7.4 Communication
Clause 7.5 Documented information Implementation Guideline
Clause 8.1 Operational planning & control
Clause 8.2 Information security risk assessment
Clause 8.3 Information security risk treatment
Clause 9.1 Performance evaluation Monitoring, measurement, analysis & evaluation
Clause 9.2 Internal audit
Clause 9.3 Management review
Clause 10.1 Non conformity and corrective action
Clause 10.2 Continual Improvement 

ISO 27001 Annex A Controls


Annex A.6 Organization of Information Security
Annex A.6.2 Mobile Devices and Teleworking
Annex A.7 Human Resource Security
Annex A.7.2 During Employment
Annex A.7.3 Termination and Change of Employment
Annex A.8 Asset Management
Annex A.8.1.3 Acceptable Use of Assets & A.8.1.4 Return of Assets
Annex A.8.2 Information Classification
Annex A.8.2.2 Labeling of Information & A.8.2.3 Handling of Assets
Annex A.8.3 Media Handling
Annex A.9 Access Control
Annex A.9.1.2 Access to Networks and Network Services
Annex A.9.2 User Access Management
Annex A.9.2.3 Management of Privileged Access Rights  
Annex A.9.2.4 Management of Secret Authentication Information of Users
Annex A.9.2.5 Review of User Access Rights 
Annex A.9.2.6 Removal or Adjustment of Access Rights
Annex A.9.3 User Responsibilities
Annex A.9.4 System and Application Access Control
Annex A.9.4.4 Use of Privileged Utility Programs 
Annex A.9.4.5 Access Control to Program Source Code
Annex A.10 Cryptography
Annex A.11 Physical and Environmental Security
Annex A.11.2 Equipment
Annex A.11.1.3 Securing Offices, Rooms and Facilities
Annex A.11.1.4 Protecting Against External and Environmental Threats
Annex A.11.1.5 Working in Secure Areas
Annex A.11.1.6 Delivery and Loading Areas
Annex A.11.2.4 Equipment Maintenance
Annex A.11.2.5 Removal of Assets
Annex A.11.2.6 Security of Kit and Assets Off-Premises
Annex A.11.2.7 Secure Disposal or Re-use of Equipment
Annex A.11.2.8 Unattended User Equipment
Annex A.11.2.9 Clear Desk and Clear Screen Policy
Annex A.12 Operations Security
Annex A.12.2 Protection from Malware
Annex A.12.3 Backup
Annex A.12.4 Logging and Monitoring
Annex A.12.5 Control of Operational Software
Annex A.12.6 Technical Vulnerability Management
Annex A.12.7 Information Systems Audit Considerations
Annex A.13 Communications Security
Annex A.13.2 Information Transfer
Annex A.13.2.3 Electronic Messaging
Annex A.13.2.4 Confidentiality or Non-Disclosure Agreements
Annex 14 System Acquisition, Development and Maintenance
Annex A.14.1.2 Securing Application Services on Public Networks
Annex A.14.1.3 Protecting Application Services Transactions
Annex A.14.2 Security in Development and Support Processes
Annex A.14.2.3 Technical Review of Applications after Operating Platform Changes
Annex A.14.2.4 Restrictions on Changes to Software Packages
Annex A.14.2.5 Secure System Engineering Principles
Annex A.14.2.6 Secure Development Environment
Annex A.14.2.7 Outsourced Development
Annex A.14.2.8 System Security Testing
Annex A.14.2.9 System Acceptance Testing
Annex A.14.3 Test data
Annex A.15 Supplier Relationships
Annex A.15.1.2 Addressing Security Within Supplier Agreements
Annex A.15.1.3 Information and Communication Technology Supply Chain
Annex A.15.2 Supplier Service Delivery Management
Annex A.16 Information Security Incident Management
Annex A.16.1.2 Reporting Information Security Events
Annex A.16.1.3 Reporting Information Security Weaknesses
Annex A.16.1.4 Assessment of and Decision on Information Security Events
Annex A.16.1.5 Response to Information Security Incidents
Annex A.16.1.6 Learning from Information Security Incidents
Annex A.16.1.7 Collection of Evidence
Annex A.17 Information Security Aspects of Business Continuity Management
Annex A.17.1.3 Verify, Review and Evaluate Information Security Continuity
Annex A.18 Compliance
Annex A.18.1.3 Protection of Records
Annex A.18.1.4 Privacy and Protection of Personally Identifiable Information
Annex A.18.1.5 Regulation of Cryptographic Controls
Annex 18.2 Information Security Reviews

About ISO 27002



This Blog Article is posted by

Infosavvy, 5B 306 Riverside Greens, Panvel, Raigad 410206 Maharashtra, India

Contact us – www.infocerts.com

https://goo.gl/maps/mHkyURHmeFXyGiVw5

Leave a Comment

Your email address will not be published.

Open Whatsapp chat
Whatsapp Us
Chat with us for faster replies.