How to Analyze the Context of the Organization and Interested Parties

ISO 27001 clauses 4.1 and 4.2: internal and external issues, interested parties and their requirements, a sample table and linking the analysis to scope, the risk register, objectives and management review.
Technical summary
Technology
ISO/IEC 27001:2022, ISO/IEC 27001:2022/Amd 1:2024, ISO 31000
Topic
Implementing and documenting clauses 4.1 and 4.2
Level
Beginner–intermediate
Prerequisites
  • The ISMS project has started
  • Access to the list of contracts and legislation
In this article7 sections

Clauses 4.1 and 4.2 are the shortest section of the standard, and the section that most often stays on paper. In many organizations, the context analysis is a SWOT table filled in once, and the interested parties list consists of the rows “customers, employees, suppliers”. The auditor opens this table, asks how it links to the scope and the risk register, and no answer comes. Below we give the method, a sample table and evidence suggestions for turning these two clauses into work that really links to scope, risk assessment and objectives.

The purpose of the context analysis

The context analysis answers the “why” question of the ISMS. Clause 4.1 requires the organization to determine the internal and external issues that are relevant to its purpose and that affect the ISMS’s ability to achieve its intended outcomes. The standard’s note states that these issues relate to the external and internal context in ISO 31000:2018 clause 5.4.1. Amendment 1, published in 2024, added to clause 4.1 that the organization shall determine whether climate change is a relevant issue, and to clause 4.2 a note that interested parties can have requirements related to climate change; the impact of this amendment on a project is explained separately in the guide to the 2022 version and 2024 amendment.

The output of the analysis is used in three places:

  • Scope (4.3): Which services, locations and processes go into the ISMS. For the details of the scope decision, see the guide defining ISO 27001 scope.
  • Risks and opportunities (6.1.1): The standard explicitly requires the issues in 4.1 and the requirements in 4.2 to be considered when planning.
  • Management review (9.3.2): Changes in internal and external issues and in the needs of interested parties are mandatory inputs.

If any one of these three links is broken, the analysis is just a file. The auditor realizes this with their first question.

Determining internal and external issues

Common tools for gathering issues are PESTLE (political, economic, social, technological, legal, environmental) for external issues and the strengths and weaknesses part of SWOT for internal issues. Which tool you choose doesn’t matter. What matters is writing down each issue’s consequence for information security. The sentence “Digitalization is increasing” adds nothing to the analysis; the sentence “The customer portal will move to the cloud in Q2, requiring decisions on identity management and data residency” becomes a direct input to the risk assessment.

Type Example issue Information security consequence
External – legal KVKK and sector regulations Personal data inventory, breach notification process
External – technological The ransomware threat intensifying in the sector Separation of backup access, restore testing
External – economic The main customer starting supplier security audits Evidence preparation, scope extension
Internal – structure The IT team consisting of two people Limited segregation of duties, compensating control
Internal – technology Server operating systems past end of support Patch management risk, migration plan
Internal – culture Shop floor staff’s habit of using shared accounts Authentication and awareness measures

The internal issues in the table are types we keep running into in the field. A critical application running on an out-of-support Windows Server or an old SLES version is a risk source in its own right because it can’t receive patches, and should be written down explicitly in the context analysis. The same goes for shared user accounts on shift terminals in production: the logs don’t show who performed an action, and incident investigation gets stuck there.

Don’t gather issues with the IT team alone. Half-hour conversations with representatives from production, sales, HR, legal and finance give far more realistic results than a list written at a desk. Attach a source to each issue (interview, contract, legislation, incident record); in the audit, you can show where the analysis came from.

Interested parties and their requirements

Clause 4.2 requires three steps: (a) determining the interested parties relevant to the ISMS, (b) determining the relevant requirements of these parties and (c) determining which of these requirements will be addressed through the ISMS. The third step was added in the 2022 revision and is the one most often skipped in the field. You don’t have to bring every requirement into the ISMS. But you do have to know which ones you’re not bringing in, and why.

A single question is enough as a filter: is this party affected by an information security decision of ours, or could it affect us? Requirements come from three sources:

  1. Legal and regulatory: Non-negotiable requirements arising from legislation.
  2. Contractual: Customer contracts, confidentiality agreements, supplier contracts, insurance policy terms.
  3. Expectations: Requests that aren’t written down but damage the relationship if not met; for example, employees expecting remote access to work without interruption.

Sample interested parties table

The table below is a fictional example for a medium-sized manufacturing or services company. In your own table, don’t leave the “In the ISMS?” column empty; the justification for a “no” is a record too.

Interested party Requirement Source In the ISMS?
Corporate customers Confidentiality, incident notification time Contract annex Yes – incident management process
Data subjects Lawful processing of data KVKK Yes – personal data controls
Employees Monitoring being transparent Privacy notice, internal policy Yes – acceptable use
IT service provider Clear instructions for access Service contract Yes – supplier access process
Insurance company MFA and backup declaration Cyber policy questionnaire Yes – control evidence
Board A predictable budget Internal expectation Partially – reported in management review
Building management CCTV recordings of common areas Lease agreement No – out of scope, justification written down

Pay particular attention to the insurance row. A box ticked “MFA on all remote access” on a cyber policy questionnaire is common in environments where part of the VPN still works with a password only. That’s a declaration risk. The person filling in the form and the person managing the firewall should look at the same table.

Add a reference column to the table linking each row to the related control, procedure or objective; that’s where traceability is built. The ISO 27001 documentation preparation work that turns requirements into written documents also draws on this table.

Linking the analysis to risks and objectives

The context and interested parties analysis is an input to the risk assessment; it isn’t a risk register itself. The link is made like this:

  • For each internal/external issue and each requirement, the question “What happens if it isn’t met?” is asked. The answer appears in the risk register as a scenario or as justification for the likelihood/impact of an existing risk.
  • Legal and contractual requirements form the evidence list for Annex A control 5.31 (legal, statutory, regulatory and contractual requirements).
  • Important requirements turn into information security objectives. The notification time in a customer contract is the basis for a measurable objective on incident response time; details of writing objectives are in the guide information security objectives.
  • Opportunities are recorded too: a new customer request can be the reason to extend the ISMS scope.

For the risk assessment method and sample records, see the ISMS risk analysis guide. The practical way to show traceability is to keep risk ID and objective ID columns in the interested parties table. The auditor starts from a contract clause and sees on a single row which risk and which control address it. End of question.

Update frequency and evidence

The standard doesn’t define a fixed frequency for the context analysis; however, under 9.3.2, changes must be considered at every management review. That’s why you should review the analysis at least as often as the management review cycle, and also trigger it on these events:

  • A new customer contract, or a change to the security annex of an existing contract
  • New legislation or a change to existing legislation
  • A major change in organizational structure, locations or core IT infrastructure
  • A serious security incident affecting the organization or the sector

The standard doesn’t require documented information for 4.1 and 4.2. However, documenting the scope (4.3) is mandatory, and the most reliable way to show the scope is based on these inputs is to keep the analysis in writing. Evidence accepted in audits: an analysis document with a version and date, brief notes of the interviews held for the analysis, an item in the management review minutes showing changes were discussed and a tracking record of actions arising from the analysis.

Common mistakes

  • Writing generic issues that could apply to any organization, not specific to the company
  • Having an interested parties list but leaving the requirements column empty
  • Not stating which requirements are addressed through the ISMS
  • The analysis’s last update date being stuck at the first certification date

If you’d like to run this work as part of setting up an ISMS, take a look at the scope of our ISO 27001 ISMS setup service. The official introduction to the standard is on the ISO/IEC 27001 page.

Frequently asked questions

Is it mandatory to use PESTLE and SWOT for the context analysis?

No. The standard doesn’t require a particular tool. PESTLE and SWOT help gather issues systematically; what matters is writing down each issue’s information security consequence and linking it to scope, risk and objectives.

Do all interested parties’ requirements need to be brought into the ISMS?

No. Clause 4.2 requires you to determine which of the requirements will be addressed through the ISMS. Writing a short justification for requirements left out shows in the audit that the decision was made consciously.

How often should the context analysis be updated?

The standard doesn’t give a fixed frequency. As management review requires changes as an input, review the analysis at least alongside the management review cycle; also update it for a new contract, a change in legislation or a major organizational change.

How does climate change relate to information security?

The 2024 amendment requires the organization to determine whether climate change is a relevant issue. From an information security perspective, the effect of flooding, extreme heat and power outages on the data center and business continuity can be assessed; if it isn’t relevant, this conclusion is recorded with its justification.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles