OpenParable
Skip to content
← Back to skills

CA-6(1)_joint-authorization-intra-organization

DevOps & Security

CA-6(1)_joint-authorization-intra-organization is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Employ a joint authorization process for the system that includes multiple authorizing officials from the same organization conducting the authorizati

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/CA_assessment-authorization-and-monitoring/CA-6(1)_joint-authorization-intra-organization/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ca-6-1-joint-authorization-intra-organization, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

CA-6(1) Joint Authorization — Intra-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 from the same organization to serve as co-authorizing officials for the system increases the level of independence in the risk-based decision-making process. It also implements the concepts of separation of duties and dual authorization as applied to the system authorization process. The intra-organization joint authorization process is most relevant for connected systems, shared systems, and systems with multiple information owners.

What to Check

  • Verify CA-6(1) Joint Authorization — Intra-organization is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for CA-6(1)
  • 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(1) 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

ToolPurposeUsage
Manual ReviewDocumentation and interview-basedN/A

Remediation Guide

Control Statement

Employ a joint authorization process for the system that includes multiple authorizing officials from the same organization conducting the authorization.

Implementation Guidance

Assigning multiple authorizing officials from the same organization to serve as co-authorizing officials for the system increases the level of independence in the risk-based decision-making process. It also implements the concepts of separation of duties and dual authorization as applied to the system authorization process. The intra-organization joint authorization process is most relevant for connected systems, shared systems, and systems with multiple information owners.

Risk Assessment

FindingSeverityImpact
CA-6(1) Joint Authorization — Intra-organization not implementedMediumAssessment, Authorization, and Monitoring
CA-6(1) partially implementedLowIncomplete Assessment, Authorization, and Monitoring

CWE Categories

CWE IDTitle
N/ANo direct CWE mapping

References

Checklist

  • Control documented in SSP
  • Implementation evidence collected
  • Operating effectiveness validated
  • Continuous monitoring in place
  • Related controls (AC-6) reviewed