Policy management, risk registers, and compliance tracking for internal GRC teams

version
0.1.0
GitHub stars
436

Install

/plugin install grc-internal@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 3

Compliance Tracker

Monitors and reports on organizational compliance posture.

Capabilities

  • Multi-Framework Tracking: Monitor SOC 2, ISO 27001, NIST, PCI, HIPAA simultaneously
  • Gap Analysis: Identify missing controls and evidence
  • Deadline Management: Track certification renewals and audit dates
  • Trend Analysis: Show compliance improvement over time

Metrics Tracked

  • Control implementation percentage by framework
  • Evidence freshness and gaps
  • Audit findings status (open/closed)
  • Policy review status
  • Training completion rates

Output Formats

  • Executive dashboard summaries
  • Detailed control matrices
  • Gap analysis reports
  • Audit readiness scorecards

Integration Points

  • Reads from compliance documentation repositories
  • Analyzes evidence folders for completeness
  • Parses audit reports for findings status
  • Uses ./grc-data/metrics/ for KPI/KRI trend lines when those records exist

Policy Lifecycle Manager

Manages policies from creation through retirement.

Capabilities

  • Policy Creation: Draft new policies from templates
  • Gap Analysis: Compare policies against framework requirements
  • Version Control: Track changes between policy versions
  • Review Scheduling: Manage annual policy review cycles
  • Approval Workflows: Document approval chains

Policy Lifecycle Stages

  1. Draft: Initial policy creation
  2. Review: Stakeholder and legal review
  3. Approve: Management approval
  4. Publish: Release to organization
  5. Monitor: Track compliance and effectiveness
  6. Update: Periodic reviews and updates
  7. Retire: End-of-life and archival

Policy Types Supported

  • Information Security Policy
  • Acceptable Use Policy
  • Data Classification Policy
  • Incident Response Policy
  • Business Continuity Policy
  • Access Control Policy
  • Change Management Policy
  • Vendor Management Policy

Output Formats

  • Policy documents (Markdown, DOCX)
  • Redlined change comparisons
  • Policy inventory matrices
  • Review schedule calendars
  • Approval documentation

Risk Register Manager

Maintains and analyzes organizational risk registers.

The register is user-owned state. Write one file per risk under ./grc-data/risks/, keep it reviewable in Git, and use schemas/risk.schema.json as the contract for JSON or JSON-equivalent YAML.

Capabilities

  • Risk Identification: Identify and categorize risks
  • Risk Scoring: Calculate inherent and residual risk scores
  • Mitigation Tracking: Monitor remediation progress
  • Risk Reporting: Generate board-level risk reports

Risk Assessment Framework

Likelihood Scale (1-5)

  1. Rare - May occur only in exceptional circumstances
  2. Unlikely - Could occur at some time
  3. Possible - Might occur at some time
  4. Likely - Will probably occur in most circumstances
  5. Almost Certain - Expected to occur in most circumstances

Impact Scale (1-5)

  1. Insignificant - No real impact
  2. Minor - Some impact, easily remediated
  3. Moderate - Significant impact requiring response
  4. Major - Major impact on operations
  5. Catastrophic - Business-threatening impact

Risk Categories

  • Strategic, Operational, Financial, Compliance
  • Technology, Security, Privacy, Third-Party
  • Reputational, Legal, Regulatory

Output Formats

  • Risk register spreadsheet format
  • Risk heat maps
  • Top 10 risks report
  • Risk trend analysis

Commands 3

Manage Risk

Maintains the organizational risk register and performs risk assessments.

Risk register entries belong in ./grc-data/risks/ and should follow docs/GRC-DATA.md plus schemas/risk.schema.json.

Arguments

  • $1 - Action (required: add, update, assess, report)
  • $2 - Risk ID or description (required for add/update)

Actions

  • add - Add a new risk to the register
  • update - Update an existing risk's status or attributes
  • assess - Perform risk assessment on a system or process
  • report - Generate risk register report

Risk Attributes

  • Risk description and category
  • Likelihood (1-5 scale)
  • Impact (1-5 scale)
  • Inherent vs residual risk scores
  • Mitigation status and owner
  • Target resolution date
  • Linked findings or controls when the risk is backed by current evidence

Example

/grc-internal:manage-risk add "Cloud misconfiguration exposure"
/grc-internal:manage-risk report

Track Compliance

Monitors and reports on compliance status across multiple frameworks.

Trend data belongs in ./grc-data/metrics/ and should follow docs/GRC-DATA.md plus schemas/metric.schema.json.

Use /grc-engineer:record-automation-metrics when you want to seed automation trend lines instead of hand-authoring JSON rows.

Arguments

  • $1 - Framework or control set (optional, defaults to all)
  • $2 - Output format (optional: summary, detailed, dashboard)

Instructions

  1. Review current compliance posture across frameworks
  2. Identify gaps and upcoming requirements
  3. Generate compliance tracking report with:
    • Overall compliance score
    • Framework-by-framework status
    • Control gaps requiring attention
    • Upcoming deadlines and renewals
    • Trend analysis

Examples

# Track SOC 2 compliance
/grc-internal:track-compliance SOC2 detailed

# Track PCI-DSS compliance
/grc-internal:track-compliance PCIDSS summary

# Track all frameworks
/grc-internal:track-compliance all dashboard

# Track ISO 27001 compliance
/grc-internal:track-compliance ISO27001 detailed

Update Policy

Manages policy documents through their lifecycle.

Arguments

  • $1 - Policy file path or name (required)
  • $2 - Action (optional: review, update, version, approve)

Actions

  • review - Analyze policy for gaps and needed updates
  • update - Suggest policy updates based on framework changes
  • version - Create new version with change tracking
  • approve - Generate approval workflow documentation

Policy Lifecycle

  1. Draft → Review → Approve → Publish → Monitor → Retire

Instructions

  1. Analyze current policy content
  2. Compare against framework requirements
  3. Identify needed updates
  4. Generate redlined changes or new version
  5. Create approval documentation

Examples

# Review general security policy
/grc-internal:update-policy "Information Security Policy.md" review

# Update policy for PCI-DSS March 2025 requirements
/grc-internal:update-policy "Access Control Policy.md" update

# Version control for compliance
/grc-internal:update-policy "Data Protection Policy.md" version

# Generate approval workflow
/grc-internal:update-policy "Incident Response Policy.md" approve

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/grc-internal
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70