Skip to content
Security
Command

/map-controls

Map controls to SOC 2 Trust Service Criteria

From plugin
trust-center
367139 skills139 commands1 MCP
Install
$ npx -y skills add GRCEngClub/claude-grc-engineering --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/map-controls

Context preview

What this command does when you run it.

Map controls to SOC 2 Trust Service Criteria

Command definition

map-controls.md
description: Map controls to SOC 2 Trust Service Criteria

Map SOC 2 Controls

Maps existing controls or implementations to SOC 2 Trust Service Criteria.

Arguments

  • `$1` - Control document or IaC file (required)
  • `$2` - Trust Service Category (optional, defaults to all)

Control Categories

Common Criteria (CC)

  • CC1: Control Environment
  • CC2: Communication and Information
  • CC3: Risk Assessment
  • CC4: Monitoring Activities
  • CC5: Control Activities
  • CC6: Logical and Physical Access
  • CC7: System Operations
  • CC8: Change Management
  • CC9: Risk Mitigation

Output

  • Control-to-criteria mapping matrix
  • Coverage analysis
  • Gap identification
  • Evidence mapping

Example

/soc2:map-controls ./policies/access-control.md CC6
Ships withtrust-center

Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.

Get the whole plugin, auto-invoked
Stats
367
Stars
0
Views
82
Forks
Active
Maintenance
JavaScript
Language
1d ago
Last commit
7mo ago
Created

Repo: GRCEngClub/claude-grc-engineering