The PSSA systematically evaluates a proposed system architecture against the SFHA failure conditions and the requirements allocated from the PASA, proposing system-level safety requirements and assumptions, and identifying safety requirements for systems, subsystems and items (including safety, reliability, independence and separation) and the FDAL and IDAL assignments. It shows where protection is needed, for example redundancy, monitors, partitioning, higher development assurance rigor, built-in test, or maintenance tasks and intervals that safety depends on, takes common cause into account and accounts for latent failures and their exposure times. It starts early, iterates with the design, allocates system safety requirements down to subsystems and items, and hands over to the SSA as designs mature.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.