Skip to content

GCRI · Cybersecurity and Digital Resilience

Safety-critical and secure software

Software and safety-critical systems engineering builds software that must not fail dangerously, in medical devices, vehicles, control systems and infrastructure. In this field it connects security to safety: secure development, verification and the assurance that software behaves as intended under attack and fault.

01Bhalisa

Safety-critical and secure software on the record.

Method recordSTEM method
  1. MethodSoftware and safety-critical systems engineering
  2. UmgciniUkhuseleko lwe-Cyber Nokomelela Kwedijithali
  3. Applied inCybersecurity and Digital Resilience
  4. Canonical pageSTEM Commons
02Isicelo

What software and safety-critical systems engineering does here.

Software and safety-critical systems engineering develops software whose failure could cause harm, loss of life or major disruption. It applies rigorous processes to control-system, medical, aviation and infrastructure software. In cyber and digital resilience and critical infrastructure, safety-critical software practice limits the chance that a software fault cascades through physical infrastructure. It informs assurance requirements for automated control in interconnected systems. The canonical description is on the STEM Commons.

Secure development life cycle

Security requirements, threat modelling, code review, testing and vulnerability handling are built into development, following practices such as the NIST Secure Software Development Framework.

Safety and security co-assurance

Hazard analysis and threat analysis are performed together so that security measures do not compromise safety functions and vice versa.

Memory-safe language transition

Components most exposed to untrusted input are identified for rewriting in memory-safe languages, which removes a large class of vulnerabilities.

03Ijografi

Connected activity in Europe.

Night lights, population density and true-colour imagery over Europe, from NASA GIBS. Each layer carries its own date.

Imephu esebenzisanayo idinga i-JavaScript; uluhlu lweeleya nemithombo zingezantsi.

Iileya 3

Connected activity, for this page

Okutsha okukhoyo

NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © abanegalelo kwi-OpenStreetMap (ODbL) · Natural Earth

Kulayishwa imifanekiso yamva nje ye-NASA.

Rhuqa ukuze uhambise. Ctrl okanye ⌘ uze ujikelezise, chophela okanye usebenzise amaqhosha ukusondeza; beka isalathisi phezu kwento ukuze ubone amaxabiso aphantsi kwaso; ukubuyisela kubuyela kummandla.

Connected activity, framed on Europe.Satellite and model products as NASA publishes them, each with its own date. They are indicators, not assessments of any place.

Data: NASA GIBS · ASTER GDEM · Blue Marble · © OpenStreetMap contributors · Natural Earth · NASA EONET · NASA HLS S30Sources and licences

  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into hexagonal cells where shown (modified). NASA open data
  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into hexagonal cells where shown (modified). NASA open data
  • VIIRS Black Marble night-time lights, NASA Goddard Space Flight Center; distributed by the NASA Level-1 and Atmosphere Archive and Distribution System (LAADS DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into hexagonal cells where shown (modified). NASA open data
  • Center for International Earth Science Information Network (CIESIN), Columbia University. 2018. Gridded Population of the World, Version 4 (GPWv4): Population Density, Revision 11. NASA Socioeconomic Data and Applications Center (SEDAC). Licensed under CC BY 4.0. Colours redrawn from the published colour map; values averaged into hexagonal cells where shown (modified). doi:10.7927/H49C6VHW. CC BY 4.0
  • VIIRS near-real-time products (flood, land surface temperature, snow cover, corrected reflectance), NASA LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into hexagonal cells where shown (modified). NASA open data
  • MODIS land products (vegetation indices, gross primary production, land cover), NASA LP DAAC and LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into hexagonal cells where shown (modified). NASA open data
  • ASTER GDEM is a product of METI and NASA (ASTER Global Digital Elevation Model V003, NASA LP DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into hexagonal cells where shown (modified). Cite as: NASA/METI/AIST/Japan Spacesystems and U.S./Japan ASTER Science Team (2019). ASTER Global Digital Elevation Model V003. doi:10.5067/ASTER/ASTGTM.003. NASA open data
  • Yenziwe nge-Natural Earth. Idatha yemephu ye-vector ne-raster esimahla @ naturalearthdata.com. Yeyoluntu
  • © OpenStreetMap contributors (ODbL), via NASA GIBS (coastlines, boundaries, roads and place names). Colours redrawn from the published colour map; values averaged into hexagonal cells where shown (modified). ODbL
  • Blue Marble, NASA Earth Observatory; imifanekiso ivela kwi-NASA GIBS. Imibala izotywe ngokutsha ukusuka kwimephu yemibala epapashiweyo; amaxabiso afakwe umndilili kwiiseli ezineheksagoni apho aboniswa khona (iguqulwe). Idatha evulekileyo ye-NASA
  • Imeko kwigloubhu nakwimephu ethe tyaba: unxweme, imida, iindlela namagama eendawo avela kwiileya zesalathiso ze-NASA GIBS (idatha ye-OpenStreetMap, ODbL, © abanegalelo kwi-OpenStreetMap); imifanekiso ye-Blue Marble njengesiseko esikhethwayo; umhlaba we-3D nokufundwa kokuphakama okuvela kwisalathiso semibala sokuphakama se-ASTER GDEM (iiklasi ezisuka kwi-5 m ukuya kwi-200 m, zandisiwe ukuze zifundeke). Imida izotywe njengoko ipapashiwe kwaye ayibonisi kuma kuwo nawuphi na ummandla.
  • Iziganeko ezenzeka ngoku: NASA Earth Observatory Natural Event Tracker (EONET); iziganeko zingumqondiso nje kwaye zigcina amakhonkco azo emithombo yokuqala.
  • Observed (EO): NASA HLS S30 (contains modified Copernicus Sentinel data 2026). We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS).
  • NASA GIBS: Siyavuma ukusebenzisa imifanekiso enikwe ziinkonzo ze-NASA's Global Imagery Browse Services (GIBS), eyinxalenye ye-NASA's Earth Science Data and Information System (ESDIS).
  • Iileya ezikhethwayo (imithombo emi-5 kuluhlu lweeleya: ephilayo, uqikelelo, eqwalaselweyo nemeko) zibonisa isincomo somboneleli wazo kwimephu nalapha xa zivuliwe; uqikelelo sisiphumo semodeli kwaye izalathisi ezivelisiweyo ziqikelelo.

Iileya nemihla

  • Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
  • Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
  • Flood water, 3-day composite: VIIRS Global Flood Product, NASA LANCE · 14 Oct 2026
  • True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026
  • Uhlobo lwesigubungelo somhlaba (IGBP), ngonyaka: MODIS Terra and Aqua isigubungelo somhlaba (MCD12Q1), NASA LP DAAC · 2024
  • Enhanced vegetation index, rolling 8 days: MODIS Terra EVI, NASA LANCE · 13 Oct 2026

04Idatha

What the method consumes.

Datasets and records used by software and safety-critical systems engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.

IdathaIndimaIleyibhile
Vulnerability reports by root causeDefect classesKUXELIWE
Static and dynamic analysis resultsCode qualityKUQWALASELWE
Hazard and threat analysesRequirementsDECLARED
05Beka iliso

Verification and test.

The screen a team would use to follow this method: its measures, states and decisions. Names are examples and values are illustrative.

Verification and test

Cybersecurity · Safety-critical and secure · Run R-2252

Test campaignGCRI · Cybersecurity and Digital Resilience

Requirements coverage

REQ-01 safe stop3211Covered
REQ-07 fault detection2017Gaps
REQ-12 timing2129Covered

Method card

Indlela yokusebenza
Software and safety-critical systems engineering
Umgangatho
traceability matrix
Reviewer
independent
Ileyibhile
KUMODELWE

Findings by severity

050100count, illustrativeIphantsiIphakathiIphezuluCritical
Verification and test: the screen's structure, terms and states for Cybersecurity.Example names and illustrative values; a design, not a record or a live system.
06Ukuqinisekiswa

How results are checked.

Software is verified through reviews, testing to defined coverage criteria and formal proofs where justified. Independent assessment examines the safety case.

CheckHow it is done
Independent verificationSafety-critical software is verified by a team independent of development
Coverage measuresTests meet stated structural coverage criteria
Vulnerability root cause trackingFixed vulnerabilities are classified by cause to improve practice

Complex software interacting with uncertain environments cannot be exhaustively tested. Updates and third-party components introduce new failure paths.

07Isilinganisi sokuphindwa nothotho lweziphumo

Model safety-critical and secure software as a system. Run the cascade.

Assembled from the Nexus Standards area profile Cyber and digital resilience law alignment: the hazards it names, the systems and sectors that carry the loss, the controls that dampen it and the data that observe it. Choose the components, pick an initiating hazard and step through the cascade. The Map view places the run on an example geography with open data. Every coupling weight is a stated assumption you can change. A teaching model, not a forecast, an assessment or a certification. To model a place of your own choosing, open the full System Builder.

Iingozi

  • Dam failure
  • Sea-ice loss
  • Coastal erosion (set off downstream)
  • River flood (set off downstream)
  • Flash flood (set off downstream)
  • Ukufuduswa kwabantu abaninzi (kubangela iziphumo ezilandelayo)
  • Biodiversity loss (set off downstream)
  • Ukuqhawuka kombane okuxhaphakileyo (kubangela iziphumo ezilandelayo)
  • Water supply shortfall (set off downstream)
  • Arctic winter sea-ice collapse (set off downstream)
  • Polar vortex disruption (set off downstream)

Izilawuli

  • NS-10 Imigaqo-nkqubo namagatya (izibophelelo ezifundeka ngoomatshini: inkcazo, ukubopha, uvavanyo nokunyanzeliswa)
  • NS-11 Ukuqinisekiswa nokubekwa kweliso (ubungqina, iziqinisekiso, uqwalaselo lokuhambelana ngaphandle kokuthemba)
  • NS-9 Ii-UNI zemeko (ukusasazwa, iimeko, iimeko zenkqubo)
  • NRS-X6 Cyber and digital security risk
  • NRS-H93 Hazard family: Identity, trust and cryptographic failure (NHS-1 cyber.identity)
  • NRS-K31 Domain pack profile: Cyber national resilience (DOMAIN-031)
  • NRS-H54 Hazard family: Signal and platform disruption (NHS-1 cyber.platform)
  • NRS-H86 Hazard family: Telecom and data-centre failure (NHS-1 infra.digital)
  • NRS-H94 Hazard family: Systemic cyber events (NHS-1 cyber.systemic-cyber)

Uqwalaselo

  • NIST National Vulnerability Database APIs (listed for reference)
  • CISA Known Exploited Vulnerabilities catalogue (listed for reference)
  • EUR-Lex Cellar (EU legal acts and delegated acts) (listed for reference)
  • Cybersecurity Supply Chain Risk Management
  • Legal measures pillar of the Global Cybersecurity Index

Umzekelo wejografi

  • North America: 243 hexagonal cells
  • Izibane zasebusuku namhlanje, ukuqhawuka kombane (VIIRS Day/Night Band), NASA GIBS
  • Amanzi aphezu komhlaba phantsi kwamafu, 30 m (OPERA DSWx-S1 radar), NASA GIBS
  • Isantya semvula, isiqingatha seyure esidlulileyo (IMERG), NASA GIBS
  • Vegetation disturbance alerts, 30 m (OPERA DIST-ALERT), NASA GIBS
09Methods and evidence

How safety-critical and secure software is modelled, measured and tested.

The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.

System model

The couplings between the systems in safety-critical and secure software: signs of influence, a reinforcing and a balancing loop, and cross-links where stress jumps.

++−+CyberIziseko zophuhliso ezibalulekileyoCommunitiesEconomyR reinforcingB balancing
Causal loop diagram from the page's systems; signs show the direction of influence. Illustrative structure for a system dynamics or network model, not estimated couplings.
FAIR guiding principles · GO FAIR and FORCE11W3C PROV · World Wide Web ConsortiumGuidance on consistent treatment of uncertainties · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
10Ubugcini

Who maintains the method.

Cybersecurity and Digital Resilience stewards software and safety-critical systems engineering for the Consortium and reviews how it is applied across platforms.

11Inkqubo yokusebenza

Indlela inkqubo eqhuba ngayo.

Process explorer · Process

Safety-critical and secure software: Risk management process

8 steps5 stages

Inkqubo yokusebenza

Safety-critical and secure software: Risk management process

ISO 31000:2018 sets out an iterative risk management process, from scope, context and criteria through assessment and treatment to monitoring, review and reporting.

  1. 01 Frame

    1. 01Scope, context and criteriaDataset · Service ownerThe frame for the process: the scope, the external and internal context, and the risk criteria. Later steps are read against this frame.
  2. 02 Risk assessment

    1. 04Risk identificationStep · Service ownerThe first part of risk assessment. Risk is usually expressed by risk sources, potential events, their consequences and likelihood.
    2. 05Risk analysisModel · Service ownerThe second part of risk assessment. It considers consequences and likelihood of the identified risks, with guidelines, not a formula.
    3. 06Risk evaluationStep · Service ownerThe last part of risk assessment. Results of the analysis are compared with the risk criteria to see where more action is needed.
  3. 03 Treatment

    1. 07Risk treatmentStep · Service ownerTreatment options are selected, then plans are prepared and implemented. Residual risk is documented and goes to monitoring and review.
  4. 04 Across the process

    1. 02Communication and consultationStep · Service ownerCommunication and consultation with stakeholders is its own process element. The standard draws it alongside the others, not in sequence.
    2. 03Monitoring and reviewStep · Service ownerMonitoring and review take place at every stage. New experience, knowledge and analysis can revise elements, actions and controls.
  5. 05 Record and report

    1. 08Recording and reportingRecord · Service ownerThe process and its outcomes are documented and reported. The standard does not name who receives the report in the clauses read.

Outline of an external standard or method, from its public sources. It describes what the framework says, not a record of any run. It does not show that Nexus or any partner performs, certifies or approves a step. A gate is a step of the method, never a Nexus approval.

12Imibuzo

Imibuzo neempendulo.

What are the limits of software and safety-critical systems engineering in this field?
Complex software interacting with uncertain environments cannot be exhaustively tested. Updates and third-party components introduce new failure paths.
How are results checked?
Software is verified through reviews, testing to defined coverage criteria and formal proofs where justified. Independent assessment examines the safety case.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method's use, not a run; no result is reported here.
Where else is this method applied?
The canonical method page lists every platform that applies it.
IingxeloNikela

Faka ubungqina obuvela kweli phepha.

Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

GCRIUkhuseleko lwe-Cyber Nokomelela KwedijithaliIinkqubo ZobuchuleImeko-mfanekiso noVavanyo loXinzelelo
Ukhuseleko lwe-Cyber Nokomelela Kwedijithali

Bring a method, a dataset or a question.

Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.