ISO 27001 Annex A 5.5 Contact With Authorities

Home / ISO 27001 Annex A Controls / ISO 27001 Annex A 5.5 Contact With Authorities

ISO 27001 Contact With Authorities

In this ultimate guide to ISO 27001 Annex A 5.5 Contact With Authorities you will learn

  • What is ISO 27001 Annex A 5.5 
  • How to implement ISO 27001 Annex A 5.5

I am Stuart Barker, the ISO 27001 Ninja and author of the Ultimate ISO 27001 Toolkit.

With over 30 years industry experience I will show you what’s new, give you ISO 27001 templates, show you examples, do a walkthrough and show you how to implement it for ISO 27001 certification.

Watch the ISO 27001 Annex A 5.5 Tutorial

If you would rather watch than read you can watch How to implement ISO 27001 Annex A 5.5 Contact With Authorities – and pass the audit

What is ISO 27001 Annex A 5.5 Contact With Authorities?

ISO 27001 Annex A 5.5 Contact with Authorities is an ISO 27001 control that requires an organisation to establish and maintain contact with authorities that are relevant to them.

ISO 27001 Annex A 5.5 Purpose

The purpose of ISO 27001 Annex A 5.5 is to ensure the appropriate flow of information takes place with respect to information security between the organisation and relevant legal, regulatory and supervisory authorities.

ISO 27001 Annex A 5.5 Definition

The ISO 27001 standard defines ISO 27001 Annex A 5.5 as

The organisation should establish and maintain contact with relevant authorities.

ISO 27001 Annex A 5.5 Contact with Authorities

DO IT YOURSELF ISO27001

Stop Spanking £10,000’s on Consultants and Platforms

ISO 27001 Toolkit Business Edition

ISO 27001 Annex A 5.5 Implementation Guide

You are going to have to ensure that:

  • you identify and document what authorities apply to you
  • in what circumstances you would contact them
  • how information security incidents should be reported if relevant
  • understand what expectations these authorities have, if any
  • include relevant contact steps in your incident management processes
  • include relevant contact steps in your business continuity and disaster recovery processes

People often scratch their heads at this one but an easy win is the contact with your data protection regulator that is likely mandated in law. In addition you can consider the likes of utility companies for power and water, health and safety if relevant, fire departments for business continuity and incident management, perhaps your telecoms provider for routing if lines go down.

Identifying the authorities we need to contact

We’re going to identify the authorities that we might need to make contact with.  Now, if you are in a regulated industry that may be relatively straightforward, there may be regulatory bodies that you might need to make contact with. 

If you’re within the European union and GDPR applies to you then you may need to  register with your local data protection authority, for example in the UK you have to register with the Information Commissioner’s Office.

The next on the list, is going to be things like the support utilities.

So, contact with authorities, the standard actually looks at things like, okay, what about water and power and things like that. These are usually things that you’ve identified as part of your Business Continuity management process  or you’ve identified as part of of your Incident Management process. So, having  contacts for those utilities and a process in Incident Management by  which you would contact them.

Obviously you’ve got things like law enforcement as well.

How to contact authorities

When it comes to how you’re going to contact them, most of these you know, it’s a no-brainer, right, you’re just going to follow whatever process they’ve got. So when it comes to documenting that, that’s kind of what you’re saying, right,  I mean when it comes to contacting the police or law enforcement we’re going to follow whatever process they’ve got. When it comes to contacting our utilities we’re going to follow whatever process that they’ve got.

It is unlikely for the majority of organisations that we have a special one to one relationship where we have our own bespoke process but in terms of the requirement of the standard you’re going to identify those authorities that you need to make contact with and how you contact them. Relatively straightforward.

Documenting contact with authorities

You’re going to list those out. You’re going to have contact details for all of those and you’re going to have the process by which you contact them, which is going to say, default, you know, follow the process that they have in place but then you’re going to bake into things like your Incident Management, your data breach, your processes where a requirement may be placed upon you to contact those authorities, you’re going to put that into the process and you’re going to call that out and document that. 

Contact with authorities ISO 27001 example

Examples of authorities that you may need to contact

  • Data protection regulator
  • Industry Regulatory Bodies
  • Government Agencies
  • Law Enforcement Agencies
  • Power Companies
  • Telecoms Companies
  • Utility Companies
  • Emergency Services

ISO 27001 Templates

The ISO 27001 Toolkit is your fast track to Do It Yourself ISO 27001 certification and includes everything you need to meet the requirements of this control.

Stuart - High Table - ISO27001 Ninja - 3

How to comply

To comply with ISO 27001 Annex A 5.5 you are going to implement the ‘how’ to the ‘what’ the control is expecting. In short measure you are going to

  • List the relevant authorities and document your who, how and when you will contact authorities

How to pass an audit

To pass an audit of ISO 27001 Annex A 5.5 Contact with Authorities you are going to make sure that you have followed the steps above in how to comply.

You are going to do that by first conducting an internal audit, following the How to Conduct an ISO 27001 Internal Audit Guide.

What the auditor will check

The audit is going to check a number of areas. Lets go through the main ones

1. That you have a list of authorities you would contact

What this means is that you need to show that you have a list of authorities that you have considered and are in scope for you.

2. That you have a process to contact them

The process may be straightforward. Many authorities have pre defined ways in which you contact them. Just write them down.

3. That you have contacted authorities

There is not an expectation that you have contacted everyone on your list. It just wont be relevant. But some of those contacts will be mandated in law or regulation, and for those, you should have evidence the contact took place. A simple example would be registering with the data protection supervisory body.

Top 3 Mistakes People Make

The top 3 Mistakes People Make for ISO 27001 Annex A 5.5 are

1. You didn’t register with the Data Protection registrar

Often a legal requirement, make sure you have registered as a data controller or data processor, which ever applies, with the relevant bodies. They will check.

2. You don’t have a list of relevant authorities

You thought it was obvious so didn’t write it down. Wrong. Write it down to show you considered it.

3. Your document and version control is wrong

Keeping your document version control up to date, making sure that version numbers match where used, having a review evidenced in the last 12 months, having documents that have no comments in are all good practices.

ISO 27001 Annex A 5.5 FAQ

Are there free templates for ISO 27001 Annex A 5.5?

There are templates for ISO 27001 Annex A 5.5 located in the ISO 27001 Toolkit.

Why is Contact with Authorities important?

Some would argue that ISO 27001 Annex A 5.5 Contact with Authorities is not that important as it is glaringly obvious. You would contact the fire department if you had a fire. You would contact the police if a crime was committed. I am not here to disagree with you. But the standard wants these things documenting so document them.
The purpose of this control is to ensure appropriate flow of information takes place with respect to information security between the organisation and relevant legal, regulatory and supervisory authorities.

ISO 27001 Annex A 5.5 sample PDF?

ISO 27001 Annex A 5.5 Sample PDF in the ISO 27001 Toolkit.

Do I have to satisfy ISO 27001 Annex A 5.5 Contact with Authorities for ISO 27001 Certification?

Yes. Clearly it is stating the bleeding obvious but this has never stopped the standard before it wont stop it now. They are explicitly required for ISO 27001.

Where can I get templates for ISO 27001 Annex A 5.5 Contact with Authorities?

ISO 27001 templates for ISO 27001 Annex A 5.5 are located in the ISO 27001 Toolkit.

How hard is ISO 27001 Annex A 5.5 Contact with Authorities?

ISO 27001 Annex A 5.5 is not hard. It is stating the bleeding obvious.

How long will ISO 27001 Annex A 5.5 Contact with Authorities take me?

ISO 27001 Annex A 5.5 will take approximately 1 hour to complete if you are starting from nothing and doing it yourself.

How much will ISO 27001 Annex A 5.5 cost me?

The cost of ISO 27001 Annex A 5.5 will depend how you go about it. If you do it yourself it will be free but will take you about 1 hour so the cost is lost opportunity cost as you tie up resource doing something that can easily be downloaded.

What are examples for ISO 27001 Annex A 5.5 Contact with Authorities?

Examples of authorities are
Utility companies
Telecoms Companies
The Police
The Fire Department
Data Protection Supervising Bodies

How do contact authorities?

As a rule you follow their prescribed process for contacting them. Anything else would be madness.

Do I have to write a list of authorities that I would contact? Really?

Yes.

Is there an online ISO 27001?

Yes, there is an online ISO 27001 at ISO 27001 Online.

ISO 27001 Controls and Attribute Values

Control typeInformation
security properties
Cybersecurity
concepts
Operational
capabilities
Security domains
PreventiveConfidentialityIdentifyGovernanceDefence
CorrectiveIntegrityProtectResilience
AvailabilityRespond
Recover

ISO 27001:2022 requirements

Organisational Controls - A5

ISO 27001 Annex A 5.1 Policies for information security

ISO 27001 Annex A 5.2 Information Security Roles and Responsibilities

ISO 27001 Annex A 5.3 Segregation of duties

ISO 27001 Annex A 5.4 Management responsibilities

ISO 27001 Annex A 5.5 Contact with authorities

ISO 27001 Annex A 5.6 Contact with special interest groups

ISO 27001 Annex A 5.7 Threat intelligence – new

ISO 27001 Annex A 5.8 Information security in project management

ISO 27001 Annex A 5.9 Inventory of information and other associated assets – change

ISO 27001 Annex A 5.10 Acceptable use of information and other associated assets – change

ISO 27001 Annex A 5.11 Return of assets

ISO 27001 Annex A 5.11 Return of assets

ISO 27001 Annex A 5.13 Labelling of information

ISO 27001 Annex A 5.14 Information transfer

ISO 27001 Annex A 5.15 Access control

ISO 27001 Annex A 5.16 Identity management

ISO 27001 Annex A 5.17 Authentication information – new

ISO 27001 Annex A 5.18 Access rights – change

ISO 27001 Annex A 5.19 Information security in supplier relationships

ISO 27001 Annex A 5.20 Addressing information security within supplier agreements

ISO 27001 Annex A 5.21 Managing information security in the ICT supply chain – new

ISO 27001 Annex A 5.22 Monitoring, review and change management of supplier services – change

ISO 27001 Annex A 5.23 Information security for use of cloud services – new

ISO 27001 Annex A 5.24 Information security incident management planning and preparation – change

ISO 27001 Annex A 5.25 Assessment and decision on information security events 

ISO 27001 Annex A 5.26 Response to information security incidents

ISO 27001 Annex A 5.27 Learning from information security incidents

ISO 27001 Annex A 5.28 Collection of evidence

ISO 27001 Annex A 5.29 Information security during disruption – change

ISO 27001 Annex A 5.31 Identification of legal, statutory, regulatory and contractual requirements

ISO 27001 Annex A 5.32 Intellectual property rights

ISO 27001 Annex A 5.33 Protection of records

ISO 27001 Annex A 5.34 Privacy and protection of PII

ISO 27001 Annex A 5.35 Independent review of information security

ISO 27001 Annex A 5.36 Compliance with policies and standards for information security

ISO 27001 Annex A 5.37 Documented operating procedures 

Technology Controls - A8

ISO 27001 Annex A 8.1 User Endpoint Devices

ISO 27001 Annex A 8.2 Privileged Access Rights

ISO 27001 Annex A 8.3 Information Access Restriction

ISO 27001 Annex A 8.4 Access To Source Code

ISO 27001 Annex A 8.5 Secure Authentication

ISO 27001 Annex A 8.6 Capacity Management

ISO 27001 Annex A 8.7 Protection Against Malware

ISO 27001 Annex A 8.8 Management of Technical Vulnerabilities

ISO 27001 Annex A 8.9 Configuration Management 

ISO 27001 Annex A 8.10 Information Deletion

ISO 27001 Annex A 8.11 Data Masking

ISO 27001 Annex A 8.12 Data Leakage Prevention

ISO 27001 Annex A 8.13 Information Backup

ISO 27001 Annex A 8.14 Redundancy of Information Processing Facilities

ISO 27001 Annex A 8.15 Logging

ISO 27001 Annex A 8.16 Monitoring Activities

ISO 27001 Annex A 8.17 Clock Synchronisation

ISO 27001 Annex A 8.18 Use of Privileged Utility Programs

ISO 27001 Annex A 8.19 Installation of Software on Operational Systems

ISO 27001 Annex A 8.20 Network Security

ISO 27001 Annex A 8.21 Security of Network Services

ISO 27001 Annex A 8.22 Segregation of Networks

ISO 27001 Annex A 8.23 Web Filtering

ISO 27001 Annex A 8.24 Use of CryptographyISO27001 Annex A 8.25 Secure Development Life Cycle

ISO 27001 Annex A 8.26 Application Security Requirements

ISO 27001 Annex A 8.27 Secure Systems Architecture and Engineering Principles

ISO 27001 Annex A 8.28 Secure Coding

ISO 27001 Annex A 8.29 Security Testing in Development and Acceptance

ISO 27001 Annex A 8.30 Outsourced Development

ISO 27001 Annex A 8.31 Separation of Development, Test and Production Environments

ISO 27001 Annex A 8.32 Change Management

ISO 27001 Annex A 8.33 Test Information

ISO 27001 Annex A 8.34 Protection of information systems during audit testing