ISO 27001 Clause 9.1 Performance evaluation Monitoring, measurement, analysis and evaluation

ISO 27001 Clause 9.1 Performance evaluation Monitoring, measurement, analysis & evaluation

Required activity

ISO 27001 Clause 9.1 Performance evaluation Monitoring, measurement, analysis & evaluation, The organization evaluates the knowledge security performance and therefore the effectiveness of the ISMS.

Implementation Guideline

The objective of monitoring and measurement is to assist the organization to gauge whether the intended outcome of data security activities including risk assessment and treatment is achieved as planned. Monitoring determines the status of a system, a process or an activity, whilst measurement may be a process to work out a worth . Thus, monitoring is often achieved through a succession of comparable measurements over a while period.

Related Products:ISO 27001 Lead Auditor Training and Certification
For monitoring and measurement, the organization establishes:
  1. What to watch and measure;
  2. Who monitors and measures
  3. Methods to be used so on produce valid results (i.e. comparable and reproducible).
For analysis and evaluation, the organization establishes:
  1. Who analyses and evaluates the results from monitoring and measurement, and when
  2. Methods to be used so on produce valid results.
There are two aspects of evaluation:
  1. Evaluating the knowledge security performance, for determining whether the organization is doing needless to say, which incorporates determining how well the processes within the ISMS meet their specifications; 
  2. Evaluating the effectiveness of the ISMS, for determining whether or not the organization is doing the proper things, which incorporates determining the extent to which information security objectives are achieved.

Note that as “as applicable” (ISO/IEC 27001:2013) means if methods for monitoring, measurement, analysis and evaluation are often determined, they have to be determined.

A good practice is to define the ‘information need’ when planning the monitoring, measurement, analysis and evaluation. An information need is typically expressed as a high-level information security question or statement that helps the organization evaluate information security performance and ISMS effectiveness. In other words, monitoring and measurement should be undertaken to realize an outlined information need.

Care should be taken when determining the attributes to be measured. it’s impracticable, costly and counterproductive to live too many, or the incorrect attributes. Besides the prices of measuring, analyzing and evaluating numerous attributes, there’s an opportunity that key issues might be obscured or missed altogether.

There are two generic sorts of measurements:
  1. Performance measurements, which express the planned leads to terms of the characteristics of the planned activity, like head counts, milestone accomplishment, or the degree to which information security controls are implemented; 
  2. Effectiveness measurements, which express the effect that realization of the planned activities has on the organization’s information security objectives.

Also Read:ISO 27001 Clause 9.2 Internal audit

It is often appropriate to spot and assign distinctive roles to those participating within the monitoring, measurement, analysis and evaluation. Those roles are often measurement client, measurement planner, measurement reviewer, information owner, information collector, information analyst and knowledge communicator of input or output of evaluation.

The responsibilities for monitoring and measurement and people for analysis and evaluation are often assigned to separate persons whom different competence is required.

Monitoring, measurement, analysis and evaluation is critical to the success of an efficient ISMS. There are variety of clauses in ISO/IEC 27001 that explicitly require determination of the effectiveness of some activities. for instance, ISO/IEC 27001:2013). Further information are often found in ISO/IEC 27004, which provides guidance on meeting the wants of ISO/IEC 27001:2013, especially, it expands on all of the concepts mentioned above, like roles and responsibilities, and forms, and provides numerous examples.

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 8.1 Operational planning & control
Clause 8.2 Information security risk assessment
Clause 8.3 Information security risk treatment
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