ISO/IEC 27028 published
ISO/IEC 27028:2026 concerns 'control attributes', in other words parameters or characteristics of controls - information security controls in fact.
ISO/IEC 27002 introduced the concept through the 'themes' and tabulated 'attributes' associated with each of the ‘reference set’ of ~93 generic infosec controls in the standard e.g.

ISO/IEC 27028 explains and expands upon the concept, emphasising the value of considering control attributes during the information treatment phase of information risk management: having decided to mitigate unacceptable risks to information using security controls, which controls are most appropriate - and why?
'Why?' is a crucial point. It's all very well ISO/IEC 27001 formally requiring that we must "determine all controls that are necessary to implement the information security risk treatment option(s) chosen" (clause 6.1.3b) but how? On what basis should we choose our necessary controls? The standard doesn't say - in fact, it doesn't even acknowledge that controls are not the only form of risk treatment since risks can also be accepted, avoided or shared (as per ISO/IEC 27005).
Other questions that might be addressed using control attributes:
What kind/s of control are most appropriate in this situation? Do we need techological/cybersecurity controls, procedures, training, oversight, some combination of those, or something else entirely?
How do various of various control options compare in terms of their costs and benefits, taking account of the entire control lifecycle?
How well do various controls align with our technical architecture, infrastructure, governance arrangements, legal obligations, policies etc.?
Which are the most dependable (least risky!) controls e.g. formally designed, conventional, proven by experience, simplest (least complex) to implement, configure, manage, monitor and maintain, and most capable of being proven effective in practice?
Are there gaps in our existing control set that should be plugged, or security issues indicating the need for control changes? If so, what forms of control are we looking for or heading towards?
Which controls could we implement entirely in-house, without the need to involve other parties? Conversely, are there controls that would take advantage of the technical skills and capabilities of our colleagues and partners, drawing us closer together?
Are all our existing controls earning their keep, in fact, or are there candidates to be retired, updated, expanded or replaced? How would we even go about identifying and evaluating them?
How important is it that our selected controls markedly reduce the risks? Would it matter if the controls were cheap and only partially effective if compensating or complementary controls could be relied upon to limit the residual risks - and if so, what would they be?
Which controls would best satisfy our compliance obligations and conformity expectations, where 'best' is some version of most cost-effective, easiest or quickest to implement, most well recognised, least disruptive, best supported etc.?
Of all our potential control options, which have the most promise in a strategic, technological, risk management or commercial sense e.g. which are the most creative and innovative sources of competitive advantage? Which controls exist in a rich and varied marketplace, as opposed to those only available (at a price!) from specialists? If we were to direct our boffins to develop an entirely new type of control product, where should they look for inspiration?
The standard illustrates the value of the approach by discussing the following non-exhaustive examples of control attributes potentially worth considering, in addition to the 4 'themes' and 5 [other] attributes in ISO/IEC 27002:
Assurance - can we trust that the control is working correctly?
Complexity - does the control have many moving parts?
Contextual-fit - does the control suit our business context?
Control environment - does the control depend on other assets?
Failure modes - if it goes wrong, will it cause or prevent a core meltdown?
Formality - are we obliged to implement the control by law?
Integration - is this a standalone control or part of something bigger?
Maturity - is it wet-behind-the-ears or wrinkly and sage?
Measurability - would we be able to monitor control operation?
Multi-functionality - does it do just one or many things?
Origin - is it a commercial product or open-source?
Regulation - must the control satisfy formal specifications, entirely?
Strength - [guess what this attribute means!]
Reduction-focused - does it reduce incident probability and/or impact?
Transparency - can someone figure out how it works?
Cost - or rather cost-effectiveness, anticipated lifetime $ value.
... and if you think of some other aspect or criteria for designing, selecting, adapting or rejecting security controls, go right ahead: the standard notes that custom attributes and/or attribute values are feasible for organisations that feel constrained by the 25 examples!
Read more about ISO/IEC 27028:2026 here on this website, or on the ISO website. License the standard from ISO or from your national standards body or sales outlet ... or by all means download my guideline covering much the same ground since 2022 (and still free!).

