What should teams document before making a tiering decision?
Handle tiering by defining the exact scope, owner, source-linked requirement, evidence artifact, and change trigger before making a public, customer-facing, audit, procurement, or internal control claim.
The useful answer is not just whether tiering is mentioned. It should explain what action is required, which source supports it, who owns it, and what evidence proves the current state.
- Define the tiering scope and source-linked trigger before assigning the work.
- Create evidence that proves the tiering decision for the specific product, service, supplier, control, certificate profile, or implementation context.
- Set a change trigger so the answer is reviewed after material source, product, supplier, platform, audit, or process changes.
Primary NIST source for cybersecurity supply chain risk management practices.
Primary NIST source for the CSF Core, Organizational Profiles, Tiers, and implementation approach.
Primary NIST source for the integrated security and privacy control catalog.