ca-6-2-joint-authorization-inter-organization

name	CA-6(2)_joint-authorization-inter-organization
description	Employ a joint authorization process for the system that includes multiple authorizing officials with at least one authorizing official from an organi
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","ca-6-2","ca","enhancement"]
tech_stack	["any"]
cwe_ids	[]
chains_with	["AC-6"]
prerequisites	["CA-6"]
severity_boost	{"AC-6":"Chain with AC-6 for comprehensive security coverage"}

CA-6(2) Joint Authorization — Inter-organization

Enhancement of: CA-6

High-Level Description

Family: Assessment, Authorization, and Monitoring (CA) Framework: NIST SP 800-53 Rev 5

Assigning multiple authorizing officials, at least one of whom comes from an external organization, to serve as co-authorizing officials for the system increases the level of independence in the risk-based decision-making process. It implements the concepts of separation of duties and dual authorization as applied to the system authorization process. Employing authorizing officials from external organizations to supplement the authorizing official from the organization that owns or hosts the system may be necessary when the external organizations have a vested interest or equities in the outcome of the authorization decision. The inter-organization joint authorization process is relevant and appropriate for connected systems, shared systems or services, and systems with multiple information owners. The authorizing officials from the external organizations are key stakeholders of the system undergoing authorization.

What to Check

• Verify CA-6(2) Joint Authorization — Inter-organization is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for CA-6(2)
• Verify enhancement builds upon base control CA-6

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for CA-6(2) 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

Employ a joint authorization process for the system that includes multiple authorizing officials with at least one authorizing official from an organization external to the organization conducting the authorization.