Terms related to trustworthiness · 3.5.10
resilience
the ability of a system to get back to an operational state quickly after an incident
What this term settles
The entry is short because it is meant to travel. It gives resilience one meaning that can be quoted in a policy without a second interpretation layer.
Who it binds
A definition binds nobody on its own, so the force of resilience comes only from the reader who adopts it in a policy, a contract, a data schema or an assurance argument.
What to do in your practice
Map the places resilience appears in policy, procurement and system records. Where the word is used without the entry behind it, add the citation or replace the sentence.
Evidence an auditor or regulator asks for
- A controlled vocabulary entry for resilience with the citation 3.5.10, an owner and a review date.An auditor can check that resilience is controlled rather than assumed.
- An assurance argument that links the property to the test, the review or the incident record behind it. The row names resilience.Shows resilience in use in the artefact the firm relies on, not only in a glossary.
- A register row with the owner, the date and the evidence reference for the claim. The record carries the resilience entry and its date.The assurance case asserts the property without naming the test, review or incident record that supports it. The gap is tested against resilience.
Common gaps this page catches
- resilience is used in the assurance argument without a written definition, so two teams can mean different things.
- The entry for resilience is reviewed when someone remembers, not on a cadence, so it drifts from the artefact it describes.
What to prepare before the amendment lands
Brief the owners who use resilience most often, then ask each to return one artefact that shows the entry in use. File the artefacts against the register row.
How to test it here
Take one live artefact rather than a template, find the sentence or field where resilience is used, and put this page beside it. Record the answer, the artefact and the date, because that record is the evidence and a glossary entry on its own is only an intention.
What this page does not claim
The page does not reproduce the standard, certify the firm or predict the wording the amendment will use; it states resilience at the claim level "definition" and stops where the public record stops.
Common questions
- What does resilience mean in ISO 22989?
- the ability of a system to get back to an operational state quickly after an incident
- What evidence should we keep for 3.5.10?
- A controlled vocabulary entry for resilience with the citation 3.5.10, an owner and a review date. An assurance argument that links the property to the test, the review or the incident record behind it. The row names resilience.
- Is resilience a requirement?
- No: resilience is a definition or clause of a terminology standard, and it becomes binding only when a firm writes it into a policy, a contract or a procedure, or when another standard incorporates it.
Related units
Source. ISO/IEC 22989:2022, Clause 3.5.10, Terms and definitions. Open the ISO public entry. Retrieved 21 October 2026.
https://www.iso.org/obp/ui/en/#iso:std:iso-iec:22989:ed-1:v1:en
ISO catalogue record 88145, the amendment status, stage and dates. Catalogue record 74296, the base standard.
Claim level: definition. The definition is in the public preview. This page states it in our own words and does not reproduce the text.
Last updated: 2026-10-21 · Markdown version · Check your vocabulary