CA-3(4)_connections-to-public-networks
DevOps & SecurityCA-3(4)_connections-to-public-networks 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.
Connections to Public Networks
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/CA_assessment-authorization-and-monitoring/CA-3(4)_connections-to-public-networks/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ca-3-4-connections-to-public-networks, 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-3(4) Connections to Public Networks
Enhancement of: CA-3
High-Level Description
Family: Assessment, Authorization, and Monitoring (CA) Framework: NIST SP 800-53 Rev 5
No description available.
What to Check
- Verify CA-3(4) Connections to Public Networks is documented in SSP
- Confirm control is operating effectively
- Review evidence of continuous monitoring for CA-3(4)
- Verify enhancement builds upon base control CA-3
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CA-3(4) 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
Refer to NIST SP 800-53 Rev 5 for the full control statement.
Implementation Guidance
Implement this control per organizational risk assessment and system categorization.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| CA-3(4) Connections to Public Networks not implemented | Medium | Assessment, Authorization, and Monitoring |
| CA-3(4) partially implemented | Low | Incomplete Assessment, Authorization, and Monitoring |
CWE Categories
| CWE ID | Title |
|---|---|
| N/A | No direct CWE mapping |
References
- NIST SP 800-53 Rev 5 - CA-3(4)
- NIST SP 800-53A Rev 5 (Assessment Procedures)
- NIST SP 800-53 Rev 5 Full Catalog
Checklist
- Control documented in SSP
- Implementation evidence collected
- Operating effectiveness validated
- Continuous monitoring in place
- Related controls (none) reviewed