What this heading covers
The six families are properties of the product, not a security programme. Confidentiality is about data not being disclosed to those without the right to see it. Integrity is about data not being changed improperly. Non-repudiation is about being unable to deny an action. Accountability is about being able to attribute an action to an entity. Authenticity is about proving an entity or a message is what it claims. Resistance is about withstanding attack. Each is measurable, and each needs evidence from the product and its operation. A penetration test result is evidence for resistance; it is not a measure of confidentiality or accountability. The draft keeps security inside the product quality model, which means the measures are about the product's behaviour, not about whether an organisation has a security management system.
Record position: characteristic 6 of 9, carrying 6 of the 40 measure families in clause 6.
What the heading asks of a team
Six properties, six kinds of evidence
An access control test evidences confidentiality. A hash check evidences integrity. An audit trail evidences accountability. One test cannot cover all six.
Product, not programme
The measures are about the product. A certification of the supplier's management system does not answer them.
Resistance has a method
Resistance needs an attack model and a test against it. A scanner output is one input, not the measure.
The common confusion
Security is often reported as a scanner result. The six families are product properties with different evidence, and a scanner covers part of resistance, not confidentiality, accountability or non-repudiation.
The measure families in this characteristic
6.7.2Confidentiality measures6.7.3Integrity measures6.7.4Non-repudiation measures6.7.5Accountability measures6.7.6Authenticity measures6.7.7Resistance measures
What to put in place before publication
- Name the data assets and the trust boundaries the security measures are about.
- Write one measure per family, with the evidence source and the population it covers.
- Record the attack model used for resistance, and the date of the last test against it.
- Check that audit records are complete enough to support the accountability and non-repudiation measures.
- Keep the security measures in the product quality report, separate from the organisational security programme.
The test a reviewer asks
- Is there at least one measure per security family, each with its own evidence?
- Does the resistance measure name the attack model and the date of the test?
Where teams usually fall short
- A scanner score presented as the security measure for all six families.
- An audit log that exists but cannot attribute an action to a person, so accountability is asserted rather than measured.
What happens next
Confidentiality, integrity and availability are the familiar three, but the draft does not put availability here; it is under reliability. Read the six pages as a set, because a control that helps one property can weaken another.
Source
ISO Online Browsing Platform, free preview of ISO/IEC DIS 25000-23.2 https://www.iso.org/obp/ui#iso:std:iso-iec:25000:-23:dis:ed-1:v2:en read 22 October 2026
ISO/IEC 25010:2023, Product quality model https://www.iso.org/standard/78176.html read 22 October 2026
ISO/IEC 25023:2016, Measurement of system and software product quality https://www.iso.org/standard/35747.html read 22 October 2026