ISO/IEC 27028 · stage 60.00 Under publication 20 October 2026 Publication window by 8 Dec 2026, our arithmetic Official record
27028ISO 27028 Revision CheckerControl attributes, recorded

Attribute record

Control type: 3 values across the catalogue

Control type describes when and how a control changes the risk of an information security incident. It answers a simple question: does the control act before the event, does it find the event while or after it happens, or does it act afterwards to reduce the damage? ISO/IEC 27002:2022 uses three values, and every one of the 93 controls carries at least one.

01Definition

What this attribute records

What the control does to the chance or the effect of an incident. It answers a specific question: where would we notice an incident, and what would we do about it?

Control type describes when and how a control changes the risk of an information security incident. It answers a simple question: does the control act before the event, does it find the event while or after it happens, or does it act afterwards to reduce the damage? ISO/IEC 27002:2022 uses three values, and every one of the 93 controls carries at least one.

The values of Control type in the published set
ValueControlsWhat it means
Preventive83Acts before an incident, to stop it happening or to make it less likely.
Detective13Acts when an incident happens or afterwards, to find and report it.
Corrective14Acts after an incident, to reduce its effect and restore the position.
02How to record

How to record it without creating a second catalogue

  • One column, values from the three published terms, separated by a semicolon where a control carries more than one.
  • The reason for a value that differs from Table A.1, in the same row, not in a separate document.
  • The evidence that the control acts at that point: a configuration, a log, a test, an incident record.
  • The review date, because a redesigned control can move from one type to another.

Errors that cost an audit

  • Treating control type as a maturity score. It describes timing, not strength.
  • Marking a control preventive because the policy says so, when the only operating evidence is a detective log.
  • Leaving a control blank because it seems to fit two types. Two values are allowed and common.
  • Using control type as a risk rating. A corrective control is not a weaker control.
03By value

The controls behind each value

Every control appears under each value it carries, so a control can appear more than once. The count is a count of rows, not a measure of strength.

Detective 13

Acts when an incident happens or afterwards, to find and report it.

5.25 5.7 6.8 7.11 7.4 8.12 8.15 8.16 8.17 8.20 8.30 8.6 8.7

Corrective 14

Acts after an incident, to reduce its effect and restore the position.

5.24 5.26 5.28 5.29 5.30 5.35 5.37 5.5 5.6 5.7 6.4 8.13 8.16 8.7

04In the record

Where this attribute is used

Each of the 93 control pages states this value in its attribute table, beside the other four. The kit exports the same value in the same column order, so a register built from it can be filtered by this attribute without reformatting. The free check uses your answer about the five attributes to place the work against your next audit.

All 93 controls The other attributes

The attribute kit, USD 799 one off. The 109-row register with all five values, the evidence list, a dated plan and the extension worksheet, as PDF, CSV and XLSX.

See the kit Open the free specimen