> For the complete documentation index, see [llms.txt](https://docs.nors.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nors.global/assessment/rcm.md). # NORS Risk & Control Matrix ## Risk & Control Matrix Overview The attached Risk and Control Matrix's (RCM) includes control objectives, risks, illustrative control activities, illustrative testing procedures and illustrative documents that could be provided as evidence during testing. The control objectives are meant to address the relevant risks that have been identified with input across the working group. Each node operator is responsible for designing their own controls to meet the control objectives. Include within this RCM are example/illustrative control activities that could be used by the node operators. Note that this is not meant to be an exhaustive, one-size fits all list and each operator's control activity set will be unique. Bespoke activities that are not identified within this document may exist that suitably meet the control objectives. It is important for node operators to consider the manner in which these activities meet the objectives and that documentation exists that serves to prove the objectives are suitably met. ## Risk & Control Matrix (RCM) Sections * **Cover sheet**: * Overview of the Node Operator Risk Standard * Columns in the RCM and their descriptions * Key additional concepts to consider throughout the document * Risk reference legend * **RCM (Risk Control Matrix)**: * Control Ojectives * Risks * Risk Reference * Illustrative Control Activity Description, Options and Examples * Illustrative Testing Procedures * Illustrative Documents for Testing Procedures * **Document Request List**: * Illustrative list of documents that could be provided as evidence during testing. ## View the RCMs ### The NORS & NORS Entry Risk & Control Matrix as of Oct 13, 2025 #### NORS [**View the NORS Risk & Control Matrix here**](https://docs.google.com/spreadsheets/d/1jFVoZu-vYwQnnf9irlPa2HrwH6z0227m/edit?usp=sharing\&ouid=109970103188700050959\&rtpof=true\&sd=true). #### NORS Entry [**View the NORS Entry Risk & Control Matrix here**](https://docs.google.com/spreadsheets/d/1FSRQRo8gBLCyZ5XpQXrkcNj2qHcIdRqXN91G-9EZ6kI/edit?usp=sharing). *The NORS Risk & Control Matrix as of August 27, 2024* [**View the NORS Risk & Control Matrix here**](https://docs.google.com/spreadsheets/d/1fG3CyDU5sWQqkmhwgQl2Iz_HxcTtRhNw/pubhtml). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nors.global/assessment/rcm.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.