ISO 27001 Annex A Organizational Control

10/21/2025
ISO 27001 Annex A Organizational control
Reading Time: 15 minutes

ISO 27001 Annex A 5.1 – Policies for Information Security

Requirements: Information security policy and topic-specific policies should be defined, approved by management, published, communicated to and acknowledged by relevant personnel and relevant interested parties, and reviewed at planned intervals and if significant changes occur.

Explanation: This control ensures everyone in the organization knows the rules for keeping information safe. The main policy sets the overall direction, while topic-specific ones cover details like access or backups. They need regular updates to match business changes, laws, or new risks, so protection stays effective.

Example: A small retail shop creates a simple policy saying all customer data must be stored securely and only shared with authorized staff. They email it to employees, who sign off, and review it yearly or after a data law change.

FAQ 1: How often should information security policies be reviewed?

Answer: Policies should be reviewed at planned intervals and whenever significant changes occur, such as business strategy shifts or new threats.

FAQ 2: Who should approve the information security policy?

Answer: Top management should approve the main policy, while topic-specific policies can be approved by appropriate personnel with authority.

FAQ 3: What should be included in the information security policy?

Answer: It should include a definition of information security, objectives, principles for activities, commitment to requirements, and procedures for handling exceptions.

ISO 27001 Annex A 5.2 – Information Security Roles and Responsibilities

Requirements: Information security roles and responsibilities should be defined and allocated according to the organization needs.

Explanation: This means assigning clear jobs for security tasks, like who protects data or handles risks. It helps everyone know their part in keeping things safe, and roles can be delegated but the main person stays accountable.

Example: In a clinic, the manager is responsible for overall data security, but delegates daily backups to the IT admin. If something goes wrong, the manager still answers for it.

FAQ 1: Who should be assigned information security responsibilities?

Answer: Information security responsibilities should be assigned to a dedicated information security officer or team, incorporating roles such as IT personnel, compliance officers, and department heads. All employees should also receive training and be made aware of their responsibilities regarding data security.

FAQ 2: How should these roles be documented?

Answer: Roles should be defined, documented, and communicated, including for asset protection and risk acceptance.

FAQ 3: What if someone lacks skills for their security role?

Answer: They should receive support to build competence and stay updated on developments related to their role.

ISO 27001 Annex A 5.3 – Segregation of Duties

Requirements: Conflicting duties and conflicting areas of responsibility should be segregated.

Explanation: Split tasks so no single person can do everything that might lead to mistakes or fraud, like approving and executing the same change. In small places, use checks like monitoring if full separation isn’t possible.

Example: In a bookstore, one employee orders books, but another checks and pays for them, preventing one person from faking orders.

FAQ 1: Why is segregation of duties important?

Answer: It prevents fraud, errors, or bypassing security by separating conflicting tasks.

FAQ 2: What if full segregation isn’t possible in a small organization?

Answer: Use compensating controls like monitoring activities or management supervision.

FAQ 3: How does this relate to role-based access?

Answer: Avoid granting conflicting roles to the same person in systems like role-based access control.

ISO 27001 Annex A 5.4 – Management Responsibilities

Requirements: Management should require all personnel to apply information security in accordance with the established information security policy, topic-specific policies and procedures of the organization.

Explanation: Leaders must support security rules and ensure staff follow them, including briefing roles, providing training, and resources. This builds a culture where everyone handles info safely.

Example: A cafe owner trains staff on not sharing customer emails and provides secure tools, checking compliance during reviews.

FAQ 1: What should management do to support security?

Answer: Demonstrate support by briefing roles, providing guidelines, and ensuring awareness.

FAQ 2: How can management ensure personnel follow policies?

Answer: Require acknowledgment of policies and provide channels for reporting violations.

FAQ 3: What resources should management provide?

Answer: Adequate resources and time for implementing security processes and controls.

ISO 27001 Annex A 5.5 – Contact with Authorities

Requirements: The organization should establish and maintain contact with relevant authorities.

Explanation: Know who to call, like police or regulators, for security issues. This helps quick reporting of incidents and staying updated on rules.

Example: A gym keeps contacts for local police in case of a data theft, and checks health data laws regularly.

FAQ 1: When should authorities be contacted?

Authorities should be contacted when there is a situation involving criminal activity, imminent danger to life or property, threats of violence, missing persons, or any other emergency that requires immediate intervention.

FAQ 2: Who are examples of relevant authorities?

Answer: Law enforcement, regulatory bodies, and supervisory authorities.

FAQ 3: Why maintain these contacts?

Answer: To support incident management, contingency planning, and anticipate regulatory changes.

ISO 27001 Annex A 5.6 – Contact with Special Interest Groups

Requirements: The organization should establish and maintain contact with special interest groups or other specialist security forums and professional associations.

Explanation: Join groups for security tips, early warnings on threats, and sharing knowledge. This keeps you informed on best practices.

Example: A bakery joins a small business security forum to learn about new scams targeting online orders.

FAQ 1: What benefits come from these contacts?

Answer: Improved knowledge of best practices, early warnings, and specialist advice.

FAQ 2: What groups should be considered?

Answer: Special interest groups, security forums, and professional associations.

FAQ 3: How can these contacts help with incidents?

Answer: They provide liaison points for dealing with security incidents.

ISO 27001 Annex A 5.7 – Threat Intelligence

Requirements: Information relating to information security threats should be collected and analysed to produce threat intelligence.

Explanation: Gather and study threat info to spot risks early. Use layers like high-level trends or specific attack details, making it relevant and actionable to prevent or reduce harm.

Example: A tutoring service subscribes to threat alerts and adjusts email filters after learning about common phishing attacks on educators.

FAQ 1: What are the layers of threat intelligence?

Answer: Strategic (high-level landscape), tactical (methodologies and tools), and operational (specific attack details).

FAQ 2: How should threat intelligence be used?

Answer: To inform risk management, update controls, and support testing processes.

FAQ 3: Where can threat intelligence come from?

Answer: Internal and external sources, analyzed for relevance and actionability.

ISO 27001 Annex A 5.8 – Information Security in Project Management

Requirements: Information security should be integrated into project management.

Explanation: Include security from the start in any project, assessing risks and testing. This covers all projects, not just tech, to avoid vulnerabilities.

Example: When launching a new website, a florist checks for data protection early, like secure payment forms.

FAQ 1: Does this apply to all projects?

Answer: Yes, regardless of type, size, or complexity, including non-ICT projects.

FAQ 2: What security aspects should be in projects?

Answer: Risk assessment, requirements like IP compliance, and testing for effectiveness.

FAQ 3: Who oversees security in projects?

Answer: Project management, with steering committees following up at stages.

ISO 27001 Annex A 5.9 – Inventory of Information and Other Associated Assets

Requirements: An inventory of information and other associated assets, including owners, should be developed and maintained.

Explanation: List all data and related items like devices, assign owners, and keep it updated. This helps protect assets by knowing what you have and who’s responsible.

Example: A hair salon lists client records, computers, and software, with the owner accountable for updates.

FAQ 1: What should be included in the inventory?

Answer: Information, hardware, software, facilities, personnel, and records.

FAQ 2: How to keep the inventory accurate?

Answer: Conduct regular reviews and automate updates during changes.

FAQ 3: What is the owner’s role?

Answer: Classify, protect, and manage risks for their assets.

ISO 27001 Annex A 5.10 – Acceptable Use of Information and Other Associated Assets

Requirements: Rules for the acceptable use and procedures for handling information and other associated assets should be identified, documented and implemented.

Explanation: Set clear rules on how to use data and tools safely, like no sharing secrets. Communicate them to prevent misuse.

Example: A coffee shop’s policy says staff can’t email customer lists home, and they sign to agree.

FAQ 1: Who needs to know acceptable use rules?

Answer: All personnel and external users accessing assets.

FAQ 2: What should procedures cover?

Answer: Access restrictions, copying, storage, and disposal.

FAQ 3: How to handle third-party assets?

Answer: Identify and control use, like through agreements.

ISO 27001 Annex A 5.11 – Return of Assets

Requirements: Personnel and other interested parties as appropriate should return all the organization’s assets in their possession upon change or termination of their employment, contract or agreement.

Explanation: When someone leaves, get back all company items like phones or data. This protects info from leaving with them.

Example: A departing mechanic returns the shop’s tablet with client info, and access is revoked.

FAQ 1: What if assets are personal property?

Answer: Transfer relevant information and securely delete from the device.

FAQ 2: How to handle knowledge upon leaving?

Answer: Document and transfer important knowledge to the organization.

FAQ 3: What assets need returning?

Answer: Devices, storage media, authentication items, and physical copies.

ISO 27001 Annex A 5.12 – Classification of Information

Requirements: Information should be classified according to the information security needs of the organization based on confidentiality, integrity, availability and relevant interested party requirements.

Explanation: Label data by importance, like “confidential” for sensitive info. Owners decide levels, reviewed over time, to apply right protection.

Example: A vet classifies pet owner details as confidential to limit access.

FAQ 1: What factors determine classification?

Answer: Confidentiality, integrity, availability, and legal requirements.

FAQ 2: Who is accountable for classification?

Answer: Owners of information assets.

FAQ 3: How often should classification be reviewed?

Answer: Periodically and with changes in value or sensitivity.

ISO 27001 Annex A 5.13 – Labelling of Information

Requirements: An appropriate set of procedures for information labelling should be developed and implemented in accordance with the information classification scheme adopted by the organization.

Explanation: Add labels like headers or metadata to show classification. This helps handle data correctly, even digitally.

Example: Emails with client info get a “confidential” footer to remind recipients.

FAQ 1: When can labelling be omitted?

Answer: Labelling can be omitted when the context is clear, such as when the content is presented in a well-defined format, or when the audience is familiar with the subject matter.

FAQ 1: When can labelling be omitted?

Answer: For non-confidential information to reduce workload.

FAQ 3: How does labelling help with automation?

Answer: Metadata enables systems to make decisions based on labels.

ISO 27001 Annex A 5.14 – Information Transfer

Requirements: Information transfer rules, procedures, or agreements should be in place for all types of transfer facilities within the organization and between the organization and other parties.

Explanation: Set rules for sending info safely, like encryption for emails or secure couriers. Cover electronic, physical, and verbal transfers to avoid leaks.

Example: A law firm uses encrypted files for client docs sent to partners.

FAQ 1: What types of transfer are covered?

Answer: Electronic, physical media, and verbal communications.

FAQ 2: How to protect electronic transfers?

Answer: Use malware detection and stronger authentication on public networks.

FAQ 3: What for physical media transfers?

Answer: Use reliable couriers and tamper-evident packaging.

ISO 27001 Annex A 5.15 – Access Control

Requirements: Rules to control physical and logical access to information and other associated assets should be established and implemented based on business and information security requirements.

Explanation: Define who gets access to what, based on needs like “need-to-know.” Use policies to prevent unauthorized entry.

Example: A library limits staff access to patron records, using logins.

FAQ 1: What principles guide access control?

Answer: Need-to-know and need-to-use.

FAQ 2: How to implement access rules?

Answer: Define consistently with classification and segregation of duties.

FAQ 3: What types of access control exist?

Answer: Mandatory, discretionary, role-based, or attribute-based.

ISO 27001 Annex A 5.16 – Identity Management

Requirements: The full life cycle of identities should be managed.

Explanation: Handle user IDs from creation to deletion, ensuring uniqueness and timely removal. This ties to access rights.

Example: A school creates unique logins for teachers, deletes them upon leaving.

FAQ 1: Why avoid shared identities?

Answer: To hold individuals accountable; use only if necessary with approval.

FAQ 2: How to handle third-party identities?

Answer: Ensure they meet trust levels and manage risks.

FAQ 3: What records should be kept?

Answer: Significant events in identity use and management.

ISO 27001 Annex A 5.17 – Authentication Information

Requirements: Allocation and management of authentication information should be controlled by a management process, including advising personnel on the appropriate handling of authentication information.

Explanation: Manage passwords or keys securely, like forcing changes and using strong ones. Advise users not to share.

Example: A bank requires new hires to change temp passwords and use complex ones.

FAQ 1: How to allocate passwords securely?

Answer: Make them unique, non-guessable, and require change on first use.

FAQ 2: What makes a strong password?

Answer: Minimum length, alphanumerics, no dictionary words.

FAQ 3: Why use password management systems?

Answer: To enforce strong passwords and prevent reuse.

ISO 27001 Annex A 5.18 – Access Rights

Requirements: Access rights to information and other associated assets should be provisioned, reviewed, modified and removed in accordance with the organization’s topic-specific policy on and rules for access control.

Explanation: Give, check, and remove access based on roles. Review regularly, especially on changes like job ends.

Example: When an employee quits a store, their POS access is immediately revoked.

FAQ 1: How to provision access rights?

Answer: Get owner approval and align with policies.

FAQ 2: When to review access rights?

Answer: Regularly, on role changes, or terminations.

FAQ 3: What if termination is sudden?

Answer: Review and revoke rights based on risk factors like reason for leaving.

ISO 27001 Annex A 5.19 – Information Security in Supplier Relationships

Requirements: Processes and procedures should be defined and implemented to manage the information security risks associated with the use of supplier’s products or services.

Explanation: Assess and control risks from suppliers, like evaluating their security and monitoring compliance.

Example: A clinic checks a software vendor’s data protection before buying.

FAQ 1: What types of suppliers to consider?

Answer: ICT, logistics, utilities, and any affecting security.

FAQ 2: How to evaluate suppliers?

Answer: Use market analysis, references, or certifications.

FAQ 3: What if a supplier doesn’t comply?

Answer: Mitigate issues or handle incidents jointly.

ISO 27001 Annex A 5.20 – Addressing Information Security Within Supplier Agreements

Requirements: Relevant information security requirements should be established and agreed with each supplier based on the type of supplier relationship.

Explanation: Include security terms in contracts, like data handling and audits, to ensure protection.

Example: A catering company adds confidentiality clauses to supplier contracts for recipes.

FAQ 1: What terms to include in agreements?

Answer: Information access, classification, and incident management.

FAQ 2: How to handle sub-contracting?

Answer: Require same obligations for sub-suppliers.

FAQ 3: What for termination?

Answer: Clauses for return of assets and ongoing confidentiality.

ISO 27001 Annex A 5.21 – Managing Information Security in the ICT Supply Chain

Requirements: Processes and procedures should be defined and implemented to manage the information security risks associated with the ICT products and services supply chain.

Explanation: Extend security to tech suppliers, like checking components for vulnerabilities.

Example: A tech firm verifies software from vendors for malware.

FAQ 1: How to propagate security in the chain?

Answer: Require suppliers to apply practices to their sub-suppliers.

FAQ 2: What to monitor in products?

Answer: Components, vulnerabilities, and proper functioning.

FAQ 3: How to handle component life cycles?

Answer: Manage risks of obsolescence with alternative suppliers.

ISO 27001 Annex A 5.22 – Monitoring, Review and Change Management of Supplier Services

Requirements: The organization should regularly monitor, review, evaluate and manage change in supplier information security practices and service delivery.

Explanation: Track supplier performance, review reports, and handle changes to keep security consistent.

Example: A hotel reviews its cleaning service’s data handling quarterly.

FAQ 1: What changes to monitor?

Answer: Enhancements, new technologies, or sub-supplier shifts.

FAQ 2: How to verify compliance?

FAQ 2: How to verify compliance? Answer: Use audits, service reports, and independent reviews.

FAQ 3: What if deficiencies are found?

Answer: Take appropriate actions to address them.

ISO 27001 Annex A 5.23 – Information Security for Use of Cloud Services

Requirements: Processes for acquisition, use, management and exit from cloud services should be established in accordance with the organization’s information security requirements.

Explanation: Plan cloud use with security in mind, like agreements on data location and exit strategies.

Example: A startup ensures its cloud provider encrypts data and allows easy export.

FAQ 1: What to define for cloud use?

Answer: Requirements, roles, and controls managed by each party.

FAQ 2: How to get assurance from providers?

Answer: Review agreements and monitor capabilities.

FAQ 3: What for exiting cloud services?

Answer: Plan handover and data return in agreements.

ISO 27001 Annex A 5.24 – Information Security Incident Management Planning and Preparation

Requirements: The organization should plan and prepare for managing information security incidents by defining, establishing and communicating information security incident management processes, roles and responsibilities.

Explanation: Set up a plan with roles for handling incidents, including reporting and response steps.

Example: A pharmacy has a plan: staff report suspicious emails to IT, who investigates.

FAQ 1: What roles are needed for incidents?

Answer: Competent personnel for detection, analysis, and response.

FAQ 2: What procedures to include?

Answer: Reporting, assessment, response, and logging.

FAQ 3: How to set objectives?

Answer: Agree with management on priorities like resolution time.

ISO 27001 Annex A 5.25 – Assessment and Decision on Information Security Events

Requirements: The organization should assess information security events and decide if they are to be categorized as information security incidents.

Explanation: Evaluate events by criteria to classify as incidents, logging details for review.

Example: A shop assesses a weird login as an incident if it’s unauthorized.

FAQ 1: What scheme to use for categorization?

Answer: Agreed criteria for consequences and priority.

FAQ 2: Who performs the assessment?

Answer: The point of contact or designated team.

FAQ 3: Why record results?

Answer: For future reference and verification.

ISO 27001 Annex A 5.26 – Response to Information Security Incidents

Requirements: Information security incidents should be responded to in accordance with the documented procedures.

Explanation: Follow steps like containing, collecting evidence, and communicating during incidents.

Example: During a virus, an office isolates infected computers and notifies staff.

FAQ 1: What should response include?

Answer: Containment, evidence collection, and escalation.

FAQ 2: Who handles responses?

Answer: A competent designated team.

FAQ 3: What after the incident?

Answer: Close, analyze root cause, and log activities.

ISO 27001 Annex A 5.27 – Learning from Information Security Incidents

Requirements: Knowledge gained from information security incidents should be used to strengthen and improve the information security controls.

Explanation: Analyze incidents to spot patterns and update plans or training to prevent repeats.

Example: After a phishing scam, a team adds email training to avoid future ones.

FAQ 1: What to monitor about incidents?

Answer: Types, volumes, and costs.

FAQ 2: How to use gained knowledge?

Answer: Update risk assessments and controls.

FAQ 3: What for user awareness?

Answer: Provide examples in training to avoid similar issues.

ISO 27001 Annex A 5.28 – Collection of Evidence

Requirements: The organization should establish and implement procedures for the identification, collection, acquisition and preservation of evidence related to information security events.

Explanation: Gather evidence properly for legal or internal use, ensuring it’s untouched.

Example: In a data breach, a firm logs all actions without altering files.

FAQ 1: Why follow evidence procedures?

Answer: To ensure admissibility in legal or disciplinary actions.

FAQ 2: What to consider in procedures?

Answer: Different media types and device statuses.

FAQ 3: How to handle cross-border evidence?

Answer: Ensure entitlement to collect across jurisdictions.

ISO 27001 Annex A 5.29 – Information Security During Disruption

Requirements: The organization should plan how to maintain information security at an appropriate level during disruption.

Explanation: Prepare for crises like outages, with plans to keep data safe and recover.

Example: A bank has backup generators and remote access for storms.

FAQ 1: What to include in plans?

Answer: Security in continuity plans and crisis management.

FAQ 2: How to test these plans?

Answer: Through exercises and simulations.

FAQ 3: What roles during disruption?

Answer: Defined responsibilities for security maintenance.

ISO 27001 Annex A 5.30 – ICT Readiness for Business Continuity

Requirements: ICT readiness should be planned, implemented, maintained and tested based on business continuity objectives and continuity requirements.

Explanation: Ensure tech systems can continue or recover quickly to support business.

Example: A delivery service tests cloud backups weekly for order data.

FAQ 1: How to align ICT readiness?

Answer: With business continuity objectives and risk assessments.

FAQ 2: What to test?

Answer: Recovery procedures and failover capabilities.

FAQ 3: How often to review?

Answer: In general, we need to review annually and after changes.

Requirements: Legal, statutory, regulatory and contractual requirements relevant to information security and the organization’s approach to meet these requirements should be identified, documented and kept up to date.

Explanation: List and follow all laws and contracts on security, updating as needed.

Example: A health clinic tracks HIPAA rules for patient data.

FAQ 1: What requirements to identify?

Answer: Legal, regulatory, and contractual related to security.

FAQ 2: How to document them?

Answer: List explicitly with the organization’s approach.

FAQ 3: Who is responsible?

Answer: Defined roles for identification and compliance.

ISO 27001 Annex A 5.32 – Intellectual Property Rights

Requirements: The organization should implement appropriate procedures to protect intellectual property rights.

Explanation: Use licensed software and protect creations with copyrights or trademarks.

Example: A designer registers logos and checks for unlicensed images.

FAQ 1: How to ensure compliance?

Answer: Maintain records of licenses and ownership.

FAQ 2: What procedures for IP?

Answer: Acquisition, usage, and monitoring for infringement.

FAQ 3: How to handle employee IP?

Answer: Agreements on ownership of work-creat

ISO 27001 Annex A 5.33 – Protection of Records

Requirements: Records should be protected from loss, destruction, falsification, unauthorized access and unauthorized release.

Explanation: Store important docs safely, following laws on retention.

Example: An accountant backs up financial records in locked cabinets.

FAQ 1: What protection methods?

Answer: Categorize, label, and handle per classification.

FAQ 2: How long to retain records?

Answer: Based on legal and business requirements.

FAQ 3: How to dispose of records?

Answer: Securely when no longer needed.

ISO 27001 Annex A 5.34 – Privacy and Protection of PII

Requirements: The organization should identify and meet the requirements regarding the preservation of privacy and protection of PII according to applicable laws and regulations and contractual requirements.

Explanation: Follow privacy laws like GDPR, assessing risks to personal data.

Example: An online store gets consent for using customer emails.

FAQ 1: How to identify requirements?

Answer: From laws, contracts, and risk assessments.

FAQ 2: What roles for PII?

Answer: Define controllers and processors.

FAQ 3: How to implement?

Answer: Through privacy impact assessments.

ISO 27001 Annex A 5.35 – Independent Review of Information Security

Requirements: The organization’s approach to managing information security and its implementation should be reviewed independently at planned intervals, or when significant changes occur.

Explanation: Get outside audits to check security effectiveness.

Example: A firm hires experts yearly to review their firewalls.

FAQ 1: How often to review?

Answer: At planned intervals (12 months) or after changes.

FAQ 2: Who conducts the review?

Answer: Independent trained personnel.

FAQ 3: What to cover?

Answer: Policies, controls, and compliance of ISO 27001

ISO 27001 Annex A 5.36 – Compliance with Policies, Rules and Standards for Information Security

Requirements: Compliance with the organization’s information security policy, topic-specific policies, rules and standards should be regularly reviewed.

Explanation: Check if everyone follows rules, using audits or tools.

Example: A company scans for policy violations monthly.

FAQ 1: Who performs compliance reviews?

Answer: Competent personnel or automated tools.

FAQ 2: What if non-compliance is found?

Answer: Address through corrective actions.

FAQ 3: How to document reviews? A

Answer: Keep records of findings and actions.

ISO 27001 Annex A 5.37 – Documented Operating Procedures

Requirements: Operating procedures for information processing facilities should be documented and made available to personnel who need them.

Explanation: Write clear steps for tasks, updating as needed, to ensure consistency.

Example: A warehouse has guides for secure inventory software use.

FAQ 1: Why document procedures?

Answer: To ensure consistency and independence from individuals.

FAQ 2: Who should have access?

Answer: Personnel needing them, kept current.

FAQ 3: How to maintain them?

Answer: Review and update with changes.

ISO 27001 Annex A Organizational control

ISO 27001 Annex A Organizational Control

Reading Time: 15 minutesISO 27001 Annex A 5.1 – Policies for Information Security Requirements: Information security policy and topic-specific policies should be defined, approved by management, published, communicated to and…
Read more
ISO 9001 Logo_Gabriel Consultant
Gabriel Consultant in ISO Consulting
Service with 20 years of experience.
ISO 14001 Certification logo
Ecovadis_Silver Badge_Gabriel Consultant
EcoVadis_Badges_Approved-Partner-2025
Find Us
© 2024 Gabriel Consultant. All rights reserved
Find Us
ISO 14001 Certification logo
ISO 9001 Logo_Gabriel Consultant
Ecovadis_Silver Badge_Gabriel Consultant
EcoVadis_Badges_Approved-Partner-2025
© 2024 Gabriel Consultant. All rights reserved
Standard

Office Hour: 9:00- 18:00

Tel : +852 23664622

Email : info@gabriel.hk

Free 30 Min Consultation Call

Request an economy and speedy way to get an ISO Certification