Concept & Requirements
Design & Development
Testing & Verification
Operations & Maintenance
Retirement & Replacement
100

Avenues of supply chain attack.

What are entry nodes?

100

Mechanisms that can be used to reduce design risk.

What are mitigation mechanisms?

100

What aspects of critical components' functionality and security requirements are (blank) (blank)?

What is actively tested?

100

Entity that can be responsible for supplying critical  materials/components that will be needed on a reoccurring basis. 

What are vendors/third-party suppliers?

100

How does the organization (blank) and (blank) the system's critical legacy subcomponents?

What is retire and replace?

200

A strategy for avoiding interruptions of critical deliveries.

What is arranging multiple alternate sources/using alternate delivery methods?

200

These items would potentially need to be reconsidered due to identified supply chain risks.

What are engineering controls?

200

A stage at which services and components can be added, calling for further supply chain risk evaluation.

What is integration?

200

An opportunity for taking only desired updates.

What is micro-pacthing?

200

Lack of this can impact the system's design and necessary supply chain controls.

What is replacement availability?

300

Guidelines, beyond baseline, that should be defined for security, performance, and verification related to desired services.

What are additional contract requirements?

300

Three possible mitigation strategies for handling insecure, insufficient, or delayed components.

What is elimination, substitution, and/or accommodation?

300

These are risk-based and need to be identified in order to ensure functionality and security of critical sytems.

What are test scenarios?

300

Services vendors can use that will have long-term persistent connections to the systems.

What are cloud services?

300

A type of risk to consider when implementing replacement systems.

What is integration risk?

400

Existing opportunities related to delivery of critical components that are needed on a reoccurring basis.

What are interruptions?

400

This must be done regarding all elements going into the product in the development process.

What is documentation?

400

These need to be met during testing stages, and if not, further development needs to take place.

What are performance benchmarks?

400

A loss connected to critical functions of systems, important to consider for future planning. 

What is contract expiration?

400

These are current ideals that can be applied to the replacement system. 

What are existing assumptions?

500

A method to validate and verify a product and the security of its components.

What is third-party testing?

500

During the development process, the organization must (blank), (blank), and (blank) critical components within the system.

What is track, receive, and store?

500

These are put in place to mitigate risks during deployment.

What are contingency plans?

500

There needs to be established processes to ensure that (blank) (blank) from updates/patches are necessary and desired.

What are applied packages?

500

A set of partners that should be informed about the retirement and replacement decisions.

What are stakeholders?

M
e
n
u