ISO-27001-Annex-A.12.6-Technical-Vulnerability-Management

ISO 27001 Annex : A.12.6 Technical Vulnerability Management

Leave a Comment / ISO 27001 La, Knowledge Base / By

ISO 27001 Annex : A.12.6  Technical Vulnerability Management Its objective is to avoid technological vulnerabilities from being exploited.

A.12.6.1  Management of Technical Vulnerabilities

Control- Information on technological vulnerabilities of information systems used should be obtained in a timely manner, the exposure of the organization to such vulnerabilities should be assessed and appropriate measures taken to address the risk involved

Implementation Guidance – An up-to-date and comprehensive asset inventory is necessary for the effective management of technical vulnerability (see Clause 8). The software vendor, version numbers, current installation status ( e.g. what the software on which systems are installed), and the person(s) within the organization responsible for the software are included in the basic details required to support technological vulnerability management.

Related Product : ISO 27001 Lead Auditor Training And Certification ISMS

In order to identify potential technical vulnerabilities, appropriate and timely action should be taken. To establish an efficient management process for technical vulnerabilities, the following guidelines should be followed:

  1. The organization should define and define technical vulnerability management roles and responsibilities, including vulnerability monitoring, risk assessment of vulnerability, asset patching, asset tracking, and any necessary coordination responsibilities.
  2. Informative resources to identify and raise awareness about the relevant technical vulnerabilities for the software and other technology (based on the asset inventory list, Refer 8.1.1), should be updated based on inventory changes and other new or useful resources;
  3. A timeline to respond to potentially relevant technical vulnerabilities notifications should be defined;
  4. The organization will recognize the associated risks and acts when a potential technological weakness has been identified; these acts may include patching compromised systems, or enforcing other controls;
  5. Actions should be carried out according to changes management protocols or following incident response procedures in information security, depending on the degree to which a technical problem needs to be handled.
  6. The risk of the installation of a patch should be measured (those risks raised by the vulnerability must be compared to the risk of installing the patch) if a patch is available from a valid source;
  7. Before downloading the patch, it must be checked and reviewed to make sure that it is safe and does not lead to side effects that can not be tolerated; other tests, such as:
  • Switching off vulnerability related services or capabilities;
  • Adapting or adding network boundary access controls, such as firewalls;
  • Enhanced surveillance for real attacks;
  • Increase vulnerability awareness;
  1. .For all procedures undertaken, an audit log should be maintained;
  2. In order to ensure its efficiency and effectiveness, the technical vulnerability management process should be monitored and assessed regularly;
  3. High-risk systems should be addressed first
  4. The incident management activities should be compatible with effective technical vulnerability management processes to relay vulnerability information to the incident response mechanism and provide appropriate procedures that may occur;
  5. Defining a procedure to tackle a situation that has identified a vulnerability, yet no appropriate countermeasure exists. The organization should in this situation assess the risks associated with the known vulnerability and define appropriate detective and corrective measures.

Also Read : ISO 27001 Annex : A.12.5 Control of Operational Software

Other Information – Technical vulnerability management can be viewed as a subfunction of change management and therefore can benefit from the processes and procedures of change management.

Vendors also have to issue patches as quickly as possible under significant pressures. So a patch can not adequately resolve the problem and has negative side effects. It is therefore possible. In some cases, it is not easy to uninstall a patch when the patch is applied.

If it is not possible to adequately test patches, for example, due to costs or lack of resources, a delay in patching can be taken into account to evaluate the associated risks, based on the experience of other users. It may be helpful to use ISO / IEC 27031.

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, a Mumbai- based institute, provides multi-domain certifications and training, which include IRCA CQI ISO 27001:2013 Lead Auditor (LA) and 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 also to illustrate the backup policy to safeguard if data gets lost due to intentional or natural hazards. It also helps you understand how to control or manage the integrity of the operating system and which software should be functioning in a business operating system. 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

A.12.6.2  Restrictions on Software Installation

Control- Users should set and implement rules governing software installation.

Implementation Guidance – Strict guidelines on what types of software users can be developed by the organization.

It would follow the concept of less privilege. Users may be able to install software if certain privileges are granted. Identifies what software installation types are permitted (e.g. software updates or security patches) and what installations are forbidden (e.g. software for personal use only and software whose malicious history is unknown or suspect). Taking into account the role of the users concerned, these privileges should be given.

Other Information- Installing software uncontrolled on computer systems may lead to vulnerabilities and information leakage, loss of integrity or other incidents of intellectual property security, or infringement of intellectual property rights.

Questions related to this topic

  1. What are the normal steps to take to remediate a vulnerable system?
  2. How do you implement a vulnerability management program?
  3. What is a vulnerability management process?
  4. How do you do a vulnerability assessment?
  5. ISO 27001 Annex : A.12.6 Technical Vulnerability Management?
  6. What are the controls used in ISO 27001 Annex : A.12.6 Technical Vulnerability Management?

ISO 27001 Requirements

Clause 4.2 Understanding the needs and expectations of interested parties 
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 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.5 Information Security Policies
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, 2nd Floor, Sai Niketan, Chandavalkar Road Opp. Gora Gandhi Hotel, Above Jumbo King, beside Speakwell Institute, Borivali West, Mumbai, Maharashtra 400092
Contact us – www.info-savvy.com
https://g.co/kgs/ttqPpZ

Leave a Comment