← Insights

Which of the 93 ISO 27001 controls touch a workforce app

Published
Author
Mian Khubaib Jim
Reading time
12 min
Topic
ISO 27001 workforce app controls
Which of the 93 ISO 27001 controls touch a workforce app
On this page10 sections · 12 min read
  1. Key Findings
  2. 1. The Question
  3. 2. The Data and the Method
  4. 3. What the Data Shows
  5. 4. What It Means for a Contractor
  6. 5. What This Does Not Show
  7. 6. Conclusion
  8. References
  9. About Operify AI
  10. Frequently Asked Questions

A buyer sends a security questionnaire and it names Annex A. Somewhere in the reply a contractor has to say what their mobile app does with an operatives data. ISO 27001 workforce app controls are not a separate list. They are a subset of the 93 controls in the standard and nobody publishes which subset.

This blog is a small research paper. One question. Every control in the annex mapped against one scope. The finding. And what it means for the person filling in the questionnaire. The control set is taken from the published standard and the tier assignment is our own work with the rule stated before the result.

Key Findings#

  • 71 of 93 controls have a workforce app surface. Mapping every Annex A control against a deskless workforce app leaves only 22 untouched. That is 76.3 per cent of the annex [1][2].
  • 43 controls produce their evidence inside the product. For those an auditor opens the system rather than a folder. That is 46.2 per cent of the annex and it is the share a contractor cannot answer with policy alone.
  • All eight people controls land. Theme A.6 has no control without a surface because every user is a deskless operative working on a client site [1].
  • Eight of the eleven controls added in 2022 sit in the product. The revision cut 114 controls to 93 and added 11. Only two of those 11 have no app surface [1][3].
  • Physical runs the other way. Theme A.7 has 14 controls and exactly one puts its evidence in the product. Eight have no surface at all.

1. The Question#

Which of the 93 controls in ISO/IEC 27001:2022 Annex A are engaged when a contractor runs a mobile workforce app and where does the evidence for each one actually live?

The annex is published in four themes [1]. Organizational controls run from A.5.1 to A.5.37 which is 37 controls. People controls run A.6.1 to A.6.8 which is 8. Physical controls run A.7.1 to A.7.14 which is 14. Technological controls run A.8.1 to A.8.34 which is 34. That totals 93.

The 2013 edition carried 114 controls in 14 domains. The 2022 edition merged and restructured them into 93 and added 11 new ones. Certificates issued against the 2013 edition stopped being valid after 31 October 2025 so every live certificate today is a 2022 certificate [3].

What nobody publishes is the subset. A questionnaire asks about an app. The standard answers about an organisation. This paper closes that gap by assigning every control to one of three places.

2. The Data and the Method#

Table 1. Sources used and what each one answers

Ref

Source

What it contains

Used for

1.1

ISO/IEC 27001:2022 Annex A [1]

93 controls across four themes of 37 and 8 and 14 and 34

The control set

1.2

ISO/IEC 27002:2022 [2]

Control guidance and five attribute types including 15 operational capabilities

Control meaning

1.3

Published transition record [3]

114 controls in 2013 and 11 added in 2022 and a deadline of 31 October 2025

Version change

1.4

ICO biometric guidance [4]

Biometric identification is special category data and a DPIA is mandatory

A.8.11 and A.5.34

1.5

ICO special category guidance [5]

What counts as special category data under UK GDPR

A.5.34

1.6

Operify AI Trust Centre [6]

Certificate 1N719TSI20261008GBRIS18Y and EU hosting and 30 day deletion

Self citation

1.7

Operify AI mapping

A tier assigned to all 93 controls under the rule in Table 2

The finding

The scope is one thing and one thing only. A mobile workforce app used by operatives on client sites together with the service behind it. Not the contractors finance system. Not the clients building. Each control is assigned to exactly one tier and the tiers are defined by where the evidence sits when an auditor asks.

Table 2. How each control was assigned

Ref

Where the evidence lives

What an auditor does

Controls

Share

2.1

In the product

Opens the system and shows a setting or a log or a record or a vendor certificate

43

46.2 per cent

2.2

In your files with the app as the subject

Opens a policy or a register or a signed document that is about the app and its users

28

30.1 per cent

2.3

No workforce app surface

Shows the same evidence whether or not the app exists

22

23.7 per cent

Assignment by Operify AI against the published Annex A control set. Each control counted once. Shares are of 93 and round to 100 per cent.

3. What the Data Shows#

3.1 Seventy One Controls Have a Surface and Forty Three Sit in the Product#

Table 3. Where the 93 controls land by theme

Ref

Theme

Controls

In the product

In your files

No surface

Has a surface

3.1

A.5 Organizational

37

11

16

10

73.0 per cent

3.2

A.6 People

8

4

4

0

100 per cent

3.3

A.7 Physical

14

1

5

8

42.9 per cent

3.4

A.8 Technological

34

27

3

4

88.2 per cent

3.5

All four themes

93

43

28

22

76.3 per cent

Calculated from the tier assignment. Has a surface sums the first two tiers.

Three quarters of the annex is engaged. That is the first useful number because most contractors assume a workforce app is a corner of the scope rather than most of it.

The second number matters more. 43 controls are answered by opening the system. A contractor who writes a good policy and runs a weak app still fails those. A contractor who buys a strong product and writes nothing fails the other 28. Neither half substitutes for the other.

The theme split is the part that surprises people. Technological controls are 88.2 per cent engaged which is expected. Physical controls are 42.9 per cent engaged which is lower than expected until you remember that the operative works inside a building the contractor does not own.

3.2 Every People Control Lands on a Deskless Workforce#

Theme A.6 is the only theme with nothing in the no surface column. Eight controls and eight hits. Four of them put the evidence straight into the product.

  • A.6.3 awareness and training. The completion record and the competency state live in the workforce system rather than in a training folder.
  • A.6.5 responsibilities after leaving. A leaver who still has a working login on Monday is the control failing in public.
  • A.6.7 remote working. Every operative is a remote worker. The app is the remote working control and not a document describing one.
  • A.6.8 event reporting. An incident raised from a phone at the point it happened is the evidence. A note written up two days later is not.

The other four sit in your files. Screening under A.6.1 and employment terms under A.6.2 and the disciplinary process under A.6.4 and confidentiality agreements under A.6.6. All four are about the people using the app so the app defines who is in scope even though it does not hold the paperwork.

3.3 Eight of the Eleven New Controls Point at the App#

The 2022 revision did not add controls at random. It added the ones a cloud era needed. Eight of the eleven land inside the product.

Table 4. The eleven controls added in 2022 and where they land

Ref

Control

Where it lands

Why

4.1

A.5.7 threat intelligence

No surface

Sits in the ISMS and not in the app

4.2

A.5.23 cloud services

In the product

The workforce app is the cloud service

4.3

A.5.30 ICT readiness for continuity

In the product

Work must continue when the signal does not

4.4

A.7.4 physical security monitoring

In your files

Patrol and entry records support it

4.5

A.8.9 configuration management

In the product

Application and tenant baselines

4.6

A.8.10 information deletion

In the product

Leaver data and retention cut off

4.7

A.8.11 data masking

In the product

Limiting what ever leaves the handset

4.8

A.8.12 data leakage prevention

In the product

Export limits and client portal scoping

4.9

A.8.16 monitoring activities

In the product

Access and anomaly monitoring

4.10

A.8.23 web filtering

No surface

Browsing control and not an app function

4.11

A.8.28 secure coding

In the product

Decided by how the app is built

Nine of the eleven have a surface of some kind. Only threat intelligence and web filtering do not. A contractor whose last ISO assessment was against the 2013 edition has never been asked most of these questions.

3.4 Three Controls Nobody Expects to Matter#

Three controls read as housekeeping in a normal office and become load bearing the moment a workforce app is in scope.

  • A.8.17 clock synchronisation. In most organisations this is a log tidiness control. In a clock in app the timestamp is the invoice. If a device clock drifts or can be set by hand then the delivery record proves nothing and the contractor has no answer when a client disputes the hours.
  • A.8.11 data masking. Face unlock on a phone feels like a convenience. The ICO is clear that biometric data used to identify a specific person is special category data and that a DPIA is mandatory before that processing starts [4][5]. It also says an alternative such as a card or a PIN should be offered and that biometric access is likely to be very hard to justify without one. Keeping the template on the device and never receiving it turns a high risk processing decision into one that was never taken.
  • A.5.30 ICT readiness for continuity. Availability is one of the three properties the standard protects. An app that stops working in a basement plant room has failed an availability control rather than missed a feature. Offline capture is a control and not a convenience.

4. What It Means for a Contractor#

Split the questionnaire before you answer it.

  • Sort the questions into two piles. Roughly 43 go to your software vendor and roughly 28 go to your own files. Answering both from the same template is why questionnaires come back.
  • Ask the vendor for the certificate and the scope. A certificate with a scope that excludes the product is a logo and not an answer.
  • Check whose certificate it is. A vendors certification covers the vendor. It does not certify the contractor buying the software.
  • Treat the leaver as a control test. A.6.5 and A.5.18 and A.8.10 all fail together on the same login.
  • Do not collect biometrics because the handset offers them. A DPIA becomes mandatory and the processing becomes high risk for a time record you could have taken another way.
  • Write offline capability into the specification. Availability is a security property and a basement with no signal is a foreseeable condition.

Most of this lands in one place. The device in an operatives hand is covered by A.7.9 for assets off premises which is the job of the mobile app module. The signed RAMS and the competency gate behind A.6.3 run through the health and safety module and the learning and competency record. Joiners and leavers under A.6.5 sit in the workforce and HR module. What the client is allowed to see under A.8.12 is set by client proof. Our own certificate and registration are published on the Trust Centre and the controls behind them on the security page. Terms used here are defined in the glossary.

5. What This Does Not Show#

  • The tiering is a judgement and not a standard. ISO publishes the controls. It does not publish a workforce app mapping. A competent auditor could move a dozen of these and still be right.
  • One scope only. A different app changes the answer. A system that also runs payroll or client billing pulls in controls this mapping leaves out.
  • Controls are counted and not weighted. A.8.5 and A.8.33 count as one each here. They are not equally important to a contractor.
  • Annex A is not the whole standard. Clauses 4 to 10 carry the management system itself and none of that is counted here. Amendment 1 published in 2024 also added a climate consideration to clause 4.
  • Certification is organisational. Nothing here says a contractor needs ISO 27001. Most do not. It says which questions an app has to answer when a buyer asks.
  • ICO guidance is under review. The biometric monitoring page is marked as under review following the Data Use and Access Act so that position may move [4].

6. Conclusion#

The answer is 71 and 43. Seventy one of the ninety three controls have a workforce app surface and forty three of them produce their evidence inside the product rather than in a policy folder.

That changes what a security questionnaire is. It is not a document exercise with a software footnote. Roughly half of it is a question about the app you bought three years ago and whether the vendor can show its work. The other half is yours and no product answers it for you.

References#

[1] ISO/IEC 27001:2022. Information security management systems. Annex A contains 93 controls in four themes of 37 organizational and 8 people and 14 physical and 34 technological. Standard page available at ISO/IEC 27001 information security (accessed October 2026).

[2] ISO/IEC 27002:2022. Information security controls. Provides guidance for each Annex A control and five attribute types including 15 operational capabilities and the cybersecurity concepts of identify and protect and detect and respond and recover. Available at ISO/IEC 27002:2022 catalogue entry (accessed October 2026).

[3] Published transition record for the 2022 revision. The 2013 edition held 114 controls in 14 domains. The 2022 edition holds 93 and adds 11 new controls. Certificates against the 2013 edition ceased to be valid after 31 October 2025 and Amendment 1 of February 2024 added a climate consideration to clause 4. Summary available at ISO 27001 version and transition summary (accessed October 2026).

[4] Information Commissioners Office. Can we use biometric data for time and access control and monitoring. Biometric identification is special category data. A DPIA is mandatory before processing begins. An alternative such as a card or PIN should be offered. Page marked as under review following the Data Use and Access Act. Available at ICO guidance on biometric time and access control (accessed October 2026).

[5] Information Commissioners Office. What is special category data. Defines the categories requiring an Article 9 condition in addition to a lawful basis. Available at ICO guidance on special category data (accessed October 2026).

[6] Operify AI. Trust Centre. Codedevza AI Ltd certified to ISO/IEC 27001:2022 under certificate 1N719TSI20261008GBRIS18Y issued 8 October 2026 and valid until 7 October 2029. Service data hosted in the European Union. Deletion requests actioned within 30 days. Self citation. Certificate verifiable at IAF CertSearch (accessed October 2026).

[7] Information Commissioners Office. Register of data protection fee payers. Entry ZB905842 for Codedevza AI Ltd. Available at ICO register entry (accessed October 2026).

[8] The ISO/IEC 27001 information security management standard. Literature review and theory based research agenda. The TQM Journal. Reviews adoption drivers and implementation outcomes across certified organisations. Indexed at Google Scholar (accessed October 2026).

[9] Operationalising Information Security Management. A procedural framework analysis of ISO/IEC 27001:2022 implementation in a financial technology organisation. Traces how individual Annex A controls are turned into operating procedure. Indexed at Google Scholar record (accessed October 2026).

[10] Extension of ISO/IEC 27001 to Mobile Devices Security Management. Examines where the standards control set meets mobile endpoints and what the gaps are. Indexed at Google Scholar listing (accessed October 2026).

[11] Operify AI. Winning More Contracts. How technology sets your cleaning business apart. Insights series. Self citation. Context on how buyers assess contractor systems. Available at the technology and contracts paper (accessed October 2026).

About Operify AI#

We sell workforce software to cleaning and security and FM contractors. That is a commercial interest in this finding and a reader should weigh it. Two things constrain it. The control set is published and any reader can run the same mapping. Section 5 states plainly that the tiering is a judgement and that a competent auditor could move a dozen of these.

Operify AI is operated by Codedevza AI Ltd company number 16485057 and registered with the ICO under ZB905842 [7]. Correspondence to hello@operifyai.co.uk.

Frequently Asked Questions

How many controls does ISO 27001 have?

The 2022 edition has 93 Annex A controls in four themes. Organizational has 37 and people has 8 and physical has 14 and technological has 34. The 2013 edition had 114 in 14 domains.

Which ISO 27001 controls apply to a workforce app?

On this mapping 71 of the 93 have a surface. Forty three produce their evidence inside the product and 28 sit in your own files with the app as the subject. Technological controls are the most engaged at 88.2 per cent and physical controls the least at 42.9 per cent.

Does my software vendors certificate make my company certified?

No. A certificate covers the organisation named on it and the scope printed on it. It answers supplier questions about the product and it does not certify the contractor buying the software.

Does a cleaning or security contractor need ISO 27001?

Usually not. It is rarely a condition of award. It becomes useful when buyers start sending security questionnaires because it answers a large part of one without a bespoke reply each time. See win more tenders for where that shows up in scoring.

What changed in the 2022 version of ISO 27001?

The control count fell from 114 to 93 through merging and restructuring and 11 new controls were added. The 14 domains became four themes. Amendment 1 in February 2024 added a climate consideration to clause 4.

When did ISO 27001:2013 certificates stop being valid?

After 31 October 2025. Every certificate in force now is against the 2022 edition. If a supplier shows you a 2013 certificate it has expired.

Can we use face recognition for clock in?

Only with care. The ICO treats biometric data used to identify a person as special category data and makes a DPIA mandatory before processing starts. It also expects a non biometric alternative such as a card or a PIN. A contractor who does not need the biometric should not take it.

Which control covers an operatives phone on a client site?

A.7.9 for security of assets off premises is the closest fit and A.8.1 for user end point devices sits beside it. Both assume the device leaves a building you control which is the normal state in this sector.

Why does clock synchronisation matter in a workforce app?

Because A.8.17 stops being a logging detail and becomes the integrity of the invoice. If a handset clock can drift or be set by hand the delivery record cannot support an hours claim. See prove service delivery and pass every audit.

Is Operify AI ISO 27001 certified and how is it priced?

Operify AI is built and operated by Codedevza AI Ltd which is certified to ISO/IEC 27001:2022 under certificate 1N719TSI20261008GBRIS18Y issued 8 October 2026. Service data is hosted in the European Union. Pricing is built around operatives and sites and the modules taken rather than a per head licence and the figure is given on the demo call. Email hello@operifyai.co.uk.

ISO 27001 workforce app controls

See the platform behind the thinking.

Thirty minutes, no slides. Bring us a contract and a hard question.

Next articleAuto-Enrolment Pension Costs: The Line Bids Forget