risk
Software and information-system failure
Failure or malfunction of operating-system, networking, or application software (defects, resource depletion, failed releases) causing loss of availability/integrity and impeding mission/business functions — including core banking/payments outages.
In catalog since 2026-09-17T22:28:00Z · Last changed 2026-09-17T22:28:00Z (f368a6cce277)
Record JSON · Open in map · Data retrieval guide
Catalog revision: 791ff2dd3a45707290badee660f185e514d15f1cf518908628f425c2f2c56ee4. A connection does not establish full coverage.
Attributes
- category
- operational
- domain
- Business Continuity & Disaster Recovery
- Secure Development (SDLC) & Application Security
- taxonomy
- iso-27005-threat
- nist-800-30-threat-source
- basel-operational-risk
- inherent_rating
- high
Details
- risk_id
- tech-software-system-failure
- category
- operational
- likelihood
- medium
- impact
- high
- inherent_rating
- high
- treatment
- mitigate
- taxonomies
- iso-27005-threat
- nist-800-30-threat-source
- basel-operational-risk
Source
No record-specific source URL is provided.
Connections
- UC-BCDR-07 — Execute recovery plans to restore systems and operations mitigates Software and information-system failure
- strength
- related
- rationale
- prioritized recovery execution restores a failed system to operational state
- UC-BCDR-11 — Sustain operations via safe modes and alternate mechanisms mitigates Software and information-system failure
- strength
- related
- rationale
- entering a defined safe mode provides graceful degradation when a system fails
- UC-SDLC-08 — Maintain current system documentation and knowledge mitigates Software and information-system failure
- strength
- related
- rationale
- Current secure-configuration and maintenance documentation reduces misconfiguration- and mishandling-driven failures.
- UC-SDLC-06 — Maintain configuration control over systems and code mitigates Software and information-system failure
- strength
- related
- rationale
- Allowing only approved, integrity-tracked changes reduces failed releases and configuration-induced failures.
- UC-BCDR-05 — Manage capacity to meet availability requirements mitigates Software and information-system failure
- strength
- related
- rationale
- capacity monitoring forestalls the resource-depletion class of system failures
- UC-ACCESS-17 — Execute, monitor, and recover production processing mitigates Software and information-system failure
- strength
- primary
- rationale
- monitoring batch/scheduled processing and resolving logged failures directly limits system-failure impact
- UC-ASSET-12 — Operate scheduled processing, backup, and availability monitoring mitigates Software and information-system failure
- strength
- primary
- rationale
- monitoring system processing and resolving failures via incident/problem management cuts the impact and duration of software/processing failures
- UC-BCDR-06 — Resolve operational incidents and eliminate root causes mitigates Software and information-system failure
- strength
- primary
- rationale
- logging, escalating, and root-causing incidents directly resolves and prevents recurring software failures
- UC-SDLC-14 — Protect production systems during audit testing mitigates Software and information-system failure
- strength
- primary
- rationale
- Limiting testers to read-only/isolated copies and scheduling tests to minimize disruption prevents audit testing from degrading production availability.
- UC-SDLC-13 — Plan solution availability and capacity mitigates Software and information-system failure
- strength
- primary
- rationale
- Availability and capacity management against forecast demand directly mitigates resource-depletion and availability system failures.
- UC-BCDR-12 — Operate IT services according to defined procedures mitigates Software and information-system failure
- strength
- related
- rationale
- monitoring operations against expected outcomes and correcting deviations catches and fixes software processing faults
- UC-SDLC-07 — Approve, test, and accept changes before production release mitigates Software and information-system failure
- strength
- primary
- rationale
- Acceptance testing in a production-representative environment plus fallback plans prevent failed releases and release-induced outages.