Clause 7.2 Competence-infosavvy

ISO 27001 Implementation Guideline for Clause 7.2, Clause 7.3 & Clause 7.4


Required activity

ISO 27001 Implementation Guideline for Clause 7.2, Clause 7.3 & Clause 7.4, The organization determines the competence of persons needed for information security performance and ensures that the persons are competent.

Implementation Guidance

Competence is that the ability to use knowledge and skills to realize intended results. it’s influenced by knowledge, experience and wisdom. Competence are often specific (e.g. about technology or specific management areas like risk management) or general (e.g. soft skills, trustworthiness, and basic technological and managerial subjects).

Competence relates to persons that employment in check of the organization. this suggests that competence should be managed for persons that are employees of the organization and for people as required. Acquisition of upper or new competence and skills are often achieved both internally and externally through experience, training (e.g. courses, seminars and workshops), mentoring, hiring or contracting external persons.

For competence that’s only temporarily needed – for a selected activity or for a brief period of your time, e.g. to hide unexpected temporary shortage of internal personnel – organizations can hire or contract external resources, whose competence is to be described and verified.

The organization should:

Determine the expected competence for every role within the ISMS and choose if it must be documented (e.g. during a job description);
Assign the roles within the ISMS to persons with the specified competence either by:

  • identifying persons within the organization who have the competence (based e.g. on their education, experience, or certifications);
  • planning and implementing actions to possess persons within the organization obtain the competence (e.g. through provision of coaching, mentoring, reassignment of current employees);
  • engaging new persons who have the competence (e.g. through hiring or contracting);

Evaluate the effectiveness of actions 

  • EXAMPLE 1 Consider if persons have acquired competence after the training.
  • EXAMPLE 2 Analyse the competence of newly hired or contracted persons a while after their arrival within the organization.
  • EXAMPLE 3 Verify if the plan for acquiring new persons has been completed needless to say.

Verify that the persons are competent for his or her roles;
Make sure that the competence evolves over time as necessary which it meets expectations.

  • Appropriate documented information is required as evidence of competence. The organization should therefore retain documentation about the required competence affecting information security performance and the way this competence is met by relevant persons.


Required activity

The persons doing work under the organization’s control are made conscious of the knowledge security policy, their contribution to the effectiveness of the ISMS, benefits of improved information security performance and implications of not conforming to the wants of the ISMS.

Implementation Guidance

Awareness of persons working under the organization’s control refers to having the required understanding and motivation about what’s expected of them with reference to information security.

Awareness concerns persons who need to know, understand, accept

  • Support the objectives stated within the information security policy;
  • Follow the principles to properly perform their daily tasks in support of data security.

Additionally, the persons doing work under the organization’s control also got to know, understand and accept the implications of not conforming with the ISMS requirements. Implications are often negative consequences for information security or repercussions for the person.

These persons got to remember that an information security policy exists and where to seek out information about it. Many staff in a corporation don’t got to know the detailed content of the policy. Instead, they ought to know, understand, accept and implement the knowledge security objectives and requirements derived from the policy that affect their job role. These requirements are often included in the standards or procedures they’re expected to follow to try to their job.

The organization should:

  • Prepare a program with the precise messages focused on each audience (e.g. internal and external persons);
  • Include information security needs and expectations within awareness and training materials on other topics to put information security needs into relevant operational contexts;
  • Prepare an idea to speak messages at planned intervals;
  • Verify the knowledge and understanding of messages both at the top of an awareness session and randomly between sessions;
  • Verify whether persons act consistent with the communicated messages and use samples of ’good’ and ’bad’ behavior to strengthen the message.

Documented information on this activity and its outcome is mandatory only within the form and to the extent the organization determines as necessary for the effectiveness of its management system (see ISO/IEC 27001:2013).


Required activity

The organization determines the requirements for internal and external communications associated with the ISMS.

Implementation Guidance

Communication may be a key process within an ISMS. Adequate communication is important with internal and external interested parties. Communications are often between internal interested parties in the least levels of the organization or between the organization and external interested parties. Communication are often initiated within the organization or by an external interested party.

Organizations got to determine:

  • Which content must be communicated, e.g. information security policies, objectives, procedures, their changes, knowledge on information security risks, requirements to suppliers and feedback on the knowledge security performance;
  • The well-liked or optimal point in time for communication activities;
  • Who is to be involved in communication activities, and which is that the audience of every communication effort;
  • Who is to initiate communication activities, e.g. specific content can require communication to be initiated by a selected person or organization;
  • Which processes are driving or initiating communication activities, and which processes are targeted or suffering from communication activities.

Communication can happen regularly or as needs arise. It are often either proactive or reactive. Communication relies on processes, channels and protocols. These should be chosen to make sure the communicated message is integrally received, correctly understood and, when relevant, acted upon appropriately.

Organizations should determine which content must be communicated, such as:

  • Plans and results of risk management to interested parties as required and appropriate, within the identification, analysis, evaluation, and treatment of the risks;
    Information security objectives;
  • Achieved information security objectives including people who can support their position within the market (e.g. ISO/IEC 27001 certificate granted; claiming conformance with personal data protection laws);
  • Incidents or crises, where transparency is usually key to preserve and increase trust and confidence within the organization’s capability to manage its information security and affect unexpected situations;
  • Roles, responsibilities and authority;
  • Information exchanged between functions and roles as needed by the ISMS’s processes;
    Changes to the ISMS;
  • Other matters identified by reviewing the controls and processes within the scope of the ISMS;
    Matters (e.g. incident or crisis notification) that need communication to regulatory bodies or other interested parties;
  • Requests or other communications from external parties like customers, potential customers, users of services and authorities.

The organization should identify the wants for communication on relevant issues:

  • Who is allowed to speak externally and internally (e.g. in special cases like a knowledge breach), allocating to specific roles with the acceptable authority. for instance, official communication officers are often defined with the acceptable authority. they might be a PR officer for external communication and a security officer for internal communication;
  • The triggers or frequency of communication (e.g. for communication of an occasion, the trigger is that the identification of the event);
  • The contents of messages for key interested parties (e.g. customers, regulators, general public, important internal users) supported high level impact scenarios. Communication are often simpler if supported messages prepared and pre-approved by an appropriate level of management as a part of a communication plan, the incident response plan or the business continuity plan;
  • The intended recipients of the communication; in some cases, an inventory should be maintained (e.g. for communicating changes to services or crisis);
  • The communication means and channels. Communication should use dedicated means and channels, to form sure that the message is official and bears the acceptable authority. Communication channels should address any needs for the protection of the confidentiality and integrity of the knowledge transmitted; and
    The designed process and therefore the method to make sure messages are sent and are correctly received and understood.

Communication should be classified and handled consistent with the organization’s requirements.

Documented information on this activity and its outcome is mandatory only within the form and to the extent the organization determines as necessary for the effectiveness of its management system (see ISO/IEC 27001:2013).

Questions related to this topic
  1. Explain ISO 27001 Implementation Guideline for Clause 7.2?
  2. Explain ISO 27001 Implementation Guideline for Clause 7.2, Clause 7.3 & Clause 7.4?
  3. Diffrence between ISO 27001 Implementation Guideline for Clause 7.2, Clause 7.3 & Clause 7.4?

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.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.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 –

2 thoughts on “ISO 27001 Implementation Guideline for Clause 7.2, Clause 7.3 & Clause 7.4”

  1. Someone essentially help to make severely articles I might state.
    That is the very first time I frequented your website page and so far?
    I amazed with the analysis you made to create this actual publish amazing.

    Fantastic task!

  2. whoah this blog is magnificent i really like studying your articles.
    Stay up the good work! You know, lots of people are searching round for this information, you could aid them greatly.

Leave a Comment

Your email address will not be published. Required fields are marked *