Zum Hauptinhalt springen
Risk source · ISO/IEC 27005

RS15 Malfunctioning software

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27005ISO 27001BSI IT-Grundschutz

A logistics company starts its week on Monday morning, yet the workstations will not boot. Overnight, the vendor of the protective software had distributed a faulty update that crashes every computer at startup. Nobody attacked, and still operations stand still until every computer has been repaired by hand, one at a time. Software does exactly what the code says, and sometimes the code contains a mistake. Without any intent, it can have the same consequences as an attack.

Malfunctioning software is a technical risk source in the sense of ISO/IEC 27005. It covers unintentional malfunctions in your own and third-party software, from programming errors to faulty updates to vulnerabilities that only an attacker brings to light.

What is behind it?

This covers every program the organization works with: operating systems, business applications, in-house software, interfaces, scripts, firmware and cloud services. Software keeps getting more complex, and much of it consists of third-party components. A bug in a small library can therefore show up in many applications at once.

How bugs arise

  • Complexity. Many functions, special cases and dependencies make it impossible to test every state.
  • Changes. Every update, every new interface and every changed configuration can break processes that used to work.
  • Time pressure in development. Tests and reviews get cut when a deadline looms.
  • Dependencies. Libraries, frameworks and third-party services bring their own bugs, which you cannot fix yourself.
  • Ageing. Software without vendor support no longer receives fixes, even when bugs and gaps are known.

Impact

Software bugs hit all protection goals. Crashes and hangs knock out availability. Calculation errors, wrong rounding or faulty data imports damage integrity, often unnoticed for a long time. Errors in authorization checks or caching show data to the wrong people and breach confidentiality. The most dangerous bugs are those that silently corrupt data, because the corrupted data travels unnoticed into the backups.

Practical examples

Rounded the wrong way. After a change to the interface between inventory management and the invoicing program, VAT is rounded incorrectly for one product group. The error is small and only surfaces months later during an audit. Hundreds of invoices have to be corrected.

Other people’s data in the customer portal. A misconfigured cache in an insurance broker’s customer portal serves logged-in customers the pages of other customers for several hours. Several customers see contracts that are not theirs and get in touch. For the broker, a notifiable data breach follows.

The creeping memory leak. A reporting service fails to release memory it has used. Every two weeks the ERP server’s memory fills up and the system freezes. Until the cause is found, only a scheduled restart helps.

Typical threats

These BSI elementary threats stem from this risk source:

Effective controls

Prevention:

Detection:

Response:

Risk sources in ISO 27005

ISO/IEC 27005 names technical risk sources as a type of their own in its definition. In Table A.10, software faults appear in several places, for example in the failure of systems, in the saturation of the information system and in tampering with software, which the standard explicitly marks as possible by accident too. Among the aspects for likelihood criteria it lists technology failure, and in the assessment it names known weaknesses and the effectiveness of existing controls as factors. To find technical vulnerabilities, Annex A.2.5.3 describes methods such as automated scanning, security testing, penetration testing and code review. The standard rates code review there as the most thorough and at the same time the most expensive method (→ ISO/IEC 27005 Information Security Risk Management).

Sources

Frequently asked questions

We do not develop software. Does this risk source still affect us?

Yes. Every organization uses software, from the operating system through accounting to cloud services, and each of these applications can contain bugs. Your influence then lies in selection, in testing updates, in contracts with vendors and in the ability to return to a working state.

Should we switch off automatic updates to avoid faulty ones?

Usually not. Updates close security gaps, and delaying them keeps you exposed for longer. A staged approach works better: a small test group first, then broad rollout, and a way back for critical systems.

How do I rate the likelihood?

Clues come from an application's bug history, the frequency of changes, the age and support status of the software and the quality of your own testing. In-house applications without automated tests and legacy systems without vendor support deserve a higher likelihood. Your own incidents and IT support tickets are the most reliable source.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.