ir-6-3-supply-chain-coordination

name	IR-6(3)_supply-chain-coordination
description	Provide incident information to the provider of the product or service and other organizations involved in the supply chain or supply chain governance
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","ir-6-3","ir","enhancement"]
tech_stack	["any"]
cwe_ids	[]
chains_with	["SR-8"]
prerequisites	["IR-6"]
severity_boost	{"SR-8":"Chain with SR-8 for comprehensive security coverage"}

IR-6(3) Supply Chain Coordination

Enhancement of: IR-6

High-Level Description

Family: Incident Response (IR) Framework: NIST SP 800-53 Rev 5

Organizations involved in supply chain activities include product developers, system integrators, manufacturers, packagers, assemblers, distributors, vendors, and resellers. Entities that provide supply chain governance include the Federal Acquisition Security Council (FASC). Supply chain incidents include compromises or breaches that involve information technology products, system components, development processes or personnel, distribution processes, or warehousing facilities. Organizations determine the appropriate information to share and consider the value gained from informing external organizations about supply chain incidents, including the ability to improve processes or to identify the root cause of an incident.

What to Check

• Verify IR-6(3) Supply Chain Coordination is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for IR-6(3)
• Verify enhancement builds upon base control IR-6

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for IR-6(3) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Tool	Purpose	Usage
Manual Review	Documentation and interview-based	N/A

Remediation Guide

Control Statement

Provide incident information to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components related to the incident.

Implementation Guidance