agentsclimarketplace

Continuous compliance

Skill onfire7777/universal-ai-skills-library/skills/continuous-compliance

Router-first AI skill system for Codex, Claude, Cursor, Hermes, Paperclip, OpenCode, and local AI stacks: search, preflight-route, and load 1,812 skills on demand without duplicating the corpus.

Install
npx -y skills add onfire7777/universal-ai-skills-library --skill continuous-compliance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Guides continuous privacy compliance monitoring implementation including automated control testing, evidence collection automation, real-time compliance dashboards, alert-based remediation workflows, regulatory change integration, and deviation management. Covers GRC platform configuration, control framework mapping, and compliance-as-code approaches. Keywords: continuous compliance, automated monitoring, evidence collection, dashboard, regulatory change, compliance-as-code.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

19.6 KB, ~4.1k tokens by cl100k_base, as published. Nobody here has run it

Continuous Privacy Compliance Monitoring

Overview

Continuous compliance monitoring replaces the traditional point-in-time audit model with an ongoing, automated approach to verifying that privacy controls are operating effectively. Rather than discovering compliance gaps during annual audits, continuous monitoring provides real-time visibility into control performance, enabling immediate remediation before gaps become regulatory violations or data breaches.

The shift from periodic to continuous monitoring is driven by several factors: the increasing frequency of regulatory changes (GDPR enforcement guidance, new US state privacy laws, sector-specific regulations), the growing complexity of data ecosystems (cloud, SaaS, APIs, third-party integrations), and supervisory authority expectations for demonstrable accountability under Art. 5(2) GDPR.

Sentinel Compliance Group implemented continuous privacy compliance monitoring in 2023, reducing time-to-detect compliance deviations from an average of 94 days (quarterly audit cycle) to 2.3 days (automated monitoring with alert-based triage).

Architecture

Three-Layer Monitoring Architecture

┌─────────────────────────────────────────────────────┐
│                 LAYER 3: REPORTING                   │
│  Executive Dashboards │ Regulatory Reports │ Alerts  │
├─────────────────────────────────────────────────────┤
│               LAYER 2: ANALYSIS                      │
│  Control Scoring │ Trend Analysis │ Risk Correlation │
├─────────────────────────────────────────────────────┤
│             LAYER 1: DATA COLLECTION                 │
│  Automated Tests │ Evidence Harvest │ External Feeds │
└─────────────────────────────────────────────────────┘

Layer 1: Data Collection

Automated Control Tests execute pre-defined checks against systems, configurations, and data:

Test CategoryData SourceTest ExamplesFrequency
Configuration ComplianceCloud APIs (AWS, Azure, GCP)Encryption at rest enabled, access logging active, data residency verifiedDaily
Access ControlIAM systems (Okta, Azure AD)Privileged access reviews current, terminated users deprovisioned, RBAC aligned with data classificationDaily
Data LifecycleDatabase metadata, storage systemsRetention periods enforced, deletion jobs executing, backup encryption verifiedDaily
Consent RecordsCMP platforms (OneTrust, Cookiebot)Consent records complete, withdrawal honored, opt-out signals processedReal-time
DSAR ProcessingDSAR management systemOpen DSARs within SLA, response quality checks, identity verification completedDaily
Vendor ComplianceVendor management platformDPAs current, certifications valid, sub-processor lists updatedWeekly
Training ComplianceLMS (Learning Management System)Training completion rates, overdue assignments, content currencyWeekly
Policy CurrencyDocument management systemPolicy review dates, approval status, version controlWeekly
Breach ReadinessIncident response toolsResponse plan current, tabletop exercise conducted, contact lists updatedMonthly
Transfer SafeguardsContract management, TIA registerSCCs executed, TIAs current, adequacy decisions monitoredWeekly

Evidence Harvesting automatically collects and timestamps compliance artifacts:

Evidence TypeCollection MethodStorageRetention
System screenshotsAutomated screenshot capture via APIEvidence repository with hash verification3 years
Configuration exportsAPI calls to target systemsVersioned configuration store3 years
Log extractsSIEM/log aggregator queriesImmutable audit log archivePer regulatory requirement
Consent recordsCMP database exportDedicated consent evidence storeDuration of processing + 5 years
DSAR recordsWorkflow system exportDSAR archive with access controls3 years after request closure
Training recordsLMS completion exportHR evidence repositoryEmployment duration + 2 years
Contract documentsContract management systemLegal document repositoryContract duration + 6 years

External Feeds ingest regulatory and threat intelligence:

Feed TypeSourcePurpose
Regulatory changesOneTrust DataGuidance, IAPP, Official JournalsDetect new laws, guidance, and enforcement actions
Enforcement actionsSupervisory authority RSS feeds, GDPRhubLearn from peer enforcement and adjust controls
Vendor risk intelligenceBitSight, SecurityScorecardMonitor vendor security posture changes
Threat intelligenceCISA, ENISA, sector ISACsCorrelate privacy risks with emerging threats

Layer 2: Analysis

Control Scoring Engine:

Each control is scored based on automated test results:

ScoreStatusDefinition
100EffectiveAll automated tests pass; evidence is current and complete
75-99Mostly EffectiveMinor deviations detected; evidence gaps exist but are non-material
50-74Partially EffectiveMaterial deviations detected; some evidence missing or outdated
25-49Largely IneffectiveMultiple failures; significant evidence gaps; control is not reliably operating
0-24IneffectiveControl is not operating; no evidence of implementation

Aggregation Logic:

  • Control Level: Average of all test results for that control (weighted by test criticality)
  • Domain Level: Weighted average of all control scores within the domain
  • Regulation Level: Weighted average of all controls mapped to a specific regulation
  • Overall Compliance Score: Weighted average of all domain scores

Trend Analysis:

  • 7-day rolling average to smooth transient deviations
  • 30-day trend to identify systematic degradation
  • Quarter-over-quarter comparison for management reporting
  • Year-over-year comparison for board reporting

Risk Correlation:

  • Cross-reference control failures with data sensitivity classifications
  • Correlate compliance deviations with recent system changes
  • Map control failures to regulatory exposure (which regulations are affected)
  • Identify compounding risks (multiple control failures in the same data flow)

Layer 3: Reporting

Real-Time Dashboards:

DashboardAudienceContentRefresh Rate
Privacy OperationsPrivacy teamControl-level scores, open deviations, DSAR metrics, vendor statusReal-time
Executive PrivacyCPO, CISO, CLODomain-level scores, trend analysis, top risks, regulatory exposureDaily
Board PrivacyBoard/Audit CommitteeOverall compliance score, year-over-year trend, peer benchmarking, material incidentsQuarterly
RegulatoryDPO, LegalRegulation-specific scores, gap details, enforcement trackerWeekly
VendorProcurement, Third-Party RiskVendor compliance scores, DPA status, certification expiryWeekly

Automated Control Testing

Control Testing Framework

For each privacy control, define:

control_id: PCC-DSAR-001
control_name: DSAR Response Timeliness
regulation_mapping:
  - GDPR Art. 12(3)
  - CCPA Section 1798.130(a)(2)
  - LGPD Art. 18
domain: Data Subject Rights
test_definition:
  test_type: data_query
  data_source: dsar_management_system
  query: |
    SELECT request_id, received_date, response_date,
           DATEDIFF(day, received_date, COALESCE(response_date, GETDATE())) as days_elapsed,
           jurisdiction, status
    FROM dsar_requests
    WHERE status IN ('open', 'in_progress', 'completed')
      AND received_date >= DATEADD(day, -90, GETDATE())
  pass_criteria:
    - field: days_elapsed
      condition: less_than_or_equal
      value: 30
      filter: "jurisdiction = 'GDPR' AND status != 'completed'"
    - field: days_elapsed
      condition: less_than_or_equal
      value: 45
      filter: "jurisdiction = 'CCPA' AND status != 'completed'"
    - field: days_elapsed
      condition: less_than_or_equal
      value: 30
      filter: "status = 'completed'"
      threshold: 0.95  # 95% of completed requests must meet deadline
  frequency: daily
  alert_threshold: 0.90  # Alert if pass rate drops below 90%
  alert_recipients:
    - [email protected]
    - [email protected]
  evidence_collection:
    - type: query_result
      description: Full DSAR status report with elapsed days
    - type: screenshot
      description: DSAR dashboard showing current queue status

Common Automated Test Patterns

Configuration Compliance Test

control_id: PCC-ENC-001
control_name: Database Encryption at Rest
test_type: api_check
data_source: aws_rds_api
check:
  api_call: describe_db_instances
  assertion: StorageEncrypted == true
  scope: all_instances
frequency: daily
remediation_automation:
  enabled: true
  action: create_jira_ticket
  priority: high
  assignee: database-team

Evidence Currency Test

control_id: PCC-DPA-001
control_name: DPA Currency
test_type: data_query
data_source: contract_management_system
query: |
  SELECT vendor_name, dpa_expiry_date,
         DATEDIFF(day, GETDATE(), dpa_expiry_date) as days_until_expiry
  FROM vendor_contracts
  WHERE contract_type = 'DPA' AND status = 'active'
pass_criteria:
  - field: days_until_expiry
    condition: greater_than
    value: 0
    description: No expired DPAs
alert_rules:
  - condition: days_until_expiry <= 30
    severity: warning
    message: "DPA for {vendor_name} expires in {days_until_expiry} days"
  - condition: days_until_expiry <= 0
    severity: critical
    message: "DPA for {vendor_name} has expired"
frequency: daily

Training Compliance Test

control_id: PCC-TRN-001
control_name: Privacy Training Completion
test_type: api_check
data_source: lms_api
check:
  api_call: get_course_completion
  course_id: PRIV-001-ANNUAL
  assertion: completion_rate >= 0.95
  scope: all_active_employees
frequency: weekly
alert_threshold: 0.90
escalation:
  - level: 1
    condition: completion_rate < 0.95
    action: notify_manager
  - level: 2
    condition: completion_rate < 0.90
    action: notify_cpo
  - level: 3
    condition: completion_rate < 0.80
    action: notify_audit_committee

Alert-Based Remediation

Alert Severity Classification

SeverityCriteriaResponse SLANotification
CriticalControl failure affecting high-sensitivity data OR regulatory deadline at risk OR active data exposure4 hoursCPO, CISO, DPO, Privacy Ops lead — immediate notification via PagerDuty/Slack
HighControl failure affecting personal data OR compliance score below threshold OR vendor DPA expired24 hoursPrivacy Ops team, control owner — email + Slack notification
MediumControl degradation (score decrease >10 points) OR evidence gap detected OR training overdue72 hoursControl owner — email notification
LowMinor deviation OR informational alert OR upcoming deadline1 weekControl owner — daily digest

Remediation Workflow

Alert Triggered
  ↓
Auto-Triage (severity classification, deduplication, correlation)
  ↓
Alert Assigned to Control Owner
  ↓
Control Owner Acknowledges (within SLA)
  ↓
Root Cause Analysis
  ↓
Remediation Plan Documented
  ↓
Remediation Executed
  ↓
Automated Re-Test
  ↓
Pass? → Alert Closed → Evidence Archived
  ↓
Fail? → Escalate → Revised Remediation Plan

Auto-Remediation

For specific control failures, automated remediation can be configured:

Control FailureAuto-Remediation ActionHuman Approval Required
Terminated user still has accessDisable account via IAM APINo (immediate)
Encryption disabled on new resourceEnable encryption via cloud APINo (immediate)
Expired DPA detectedGenerate renewal notification to vendor managerYes (notification only)
Training overdue > 30 daysSend automated reminder to employee and managerNo (notification)
Consent record missing timestampFlag record for manual reviewYes (review required)
DSAR approaching SLA deadlineEscalate to privacy operations leadNo (escalation only)

Regulatory Change Integration

Regulatory Change Management Process

External Regulatory Feed
  ↓
Change Detection (new law, amendment, guidance, enforcement action)
  ↓
Relevance Assessment (automated keyword matching + manual review)
  ↓
Impact Analysis (which controls, processes, and systems are affected)
  ↓
Gap Assessment (current compliance vs. new requirement)
  ↓
Remediation Planning (control updates, policy changes, system modifications)
  ↓
Implementation and Testing
  ↓
Control Framework Updated
  ↓
Monitoring Rules Adjusted

Regulatory Change Categories

CategoryResponse TimelineExample
New regulation enactedAssessment within 30 days; implementation by effective dateNew US state privacy law with 12-month implementation window
Existing regulation amendedAssessment within 14 days; implementation per amendment effective dateGDPR delegated act modifying adequacy decision
Supervisory authority guidanceAssessment within 30 days; implementation within 90 daysEDPB guidelines on consent for cookie walls
Enforcement action (peer)Lessons-learned review within 14 days; control gap check within 30 daysDPA fine for inadequate DSAR response process
Court decisionLegal review within 14 days; impact assessment within 30 daysCJEU judgment invalidating transfer mechanism

Control Framework Versioning

When regulatory changes require control updates:

  1. Document the regulatory change and its impact on existing controls
  2. Draft updated control definitions and test criteria
  3. Review and approve changes through the privacy governance committee
  4. Update automated test configurations
  5. Re-baseline compliance scores (distinguish between score changes due to new requirements vs. degradation)
  6. Communicate changes to control owners and affected stakeholders

Compliance-as-Code

Infrastructure Privacy Compliance

Embed privacy compliance checks into infrastructure-as-code (IaC) pipelines:

# Example: Terraform compliance policy for data residency
policy "data_residency_eu" {
  description = "Ensure EU personal data is stored in EU regions only"
  enforcement_level = "mandatory"

  rule "storage_location" {
    condition = resource.aws_s3_bucket.region in ["eu-west-1", "eu-central-1", "eu-north-1"]
    message   = "S3 buckets containing EU personal data must be in EU regions"
  }

  rule "encryption_required" {
    condition = resource.aws_s3_bucket.server_side_encryption_configuration != null
    message   = "S3 buckets containing personal data must have encryption enabled"
  }

  rule "versioning_enabled" {
    condition = resource.aws_s3_bucket.versioning[0].enabled == true
    message   = "S3 buckets containing personal data must have versioning enabled for audit trail"
  }

  rule "public_access_blocked" {
    condition = resource.aws_s3_bucket_public_access_block.block_public_acls == true
    message   = "S3 buckets containing personal data must block public access"
  }
}

Application Privacy Compliance

Integrate privacy checks into CI/CD pipelines:

Pipeline StagePrivacy CheckBlocking?
Code ReviewPII detection in code comments, logs, and test dataYes
Static AnalysisPrivacy annotation verification (data classification, retention, purpose)Yes
BuildDependency check for privacy-impacting librariesWarning
Integration TestConsent enforcement verification, DSAR endpoint testingYes
Pre-DeployData residency verification, encryption verificationYes
Post-DeployPrivacy header verification, cookie consent verificationMonitoring

Dashboard Design

Executive Dashboard Components

Overall Compliance Score (large numeric display):

  • Current score: 94.2%
  • 30-day trend: +1.3%
  • Target: 95%

Compliance by Regulation (horizontal bar chart):

GDPR:         ████████████████████░  96%
CCPA/CPRA:    ███████████████████░░  93%
LGPD:         ██████████████████░░░  91%
PIPA:         ████████████████████░  97%
UK GDPR:      ███████████████████░░  94%

Open Deviations by Severity (donut chart):

  • Critical: 0
  • High: 2
  • Medium: 8
  • Low: 15

Control Health Heatmap (10x grid, one cell per domain):

  • Green (>90%): Privacy Governance, Risk Management, Incident Management, Training
  • Yellow (75-90%): Data Inventory, Regulatory, DSR, Consent, Third-Party
  • Red (<75%): None
  • Grey: Privacy by Design (assessment in progress)

Top 5 Deviations Requiring Attention (table):

IDControlScoreDays OpenOwner
DEV-2025-089Vendor DPA Renewal (Vendor X)012Procurement
DEV-2025-091DSAR Response SLA (LGPD)675Privacy Ops
DEV-2025-088Training Completion (Engineering)8821L&D
DEV-2025-092Cookie Consent Banner (FR site)723Marketing
DEV-2025-087Retention Job Failure (Archive DB)508Data Engineering

Sentinel Compliance Group Implementation

  • Platform: OneTrust GRC for compliance management; custom Python automation layer for evidence harvesting; Grafana for dashboards
  • Controls Monitored: 312 privacy controls across 10 domains, mapped to GDPR, CCPA/CPRA, LGPD, PIPA, and UK GDPR
  • Automated Tests: 478 automated test cases executing daily/weekly per schedule
  • Evidence Collection: 12,400 evidence artifacts automatically collected per quarter
  • Alert Volume: Average 23 alerts per week (2 high, 7 medium, 14 low); average resolution time: 2.3 days
  • Overall Compliance Score: 94.2% (December 2024), up from 87.1% at program launch (January 2024)
  • Audit Impact: External auditors (SOC 2 and ISO 27701) accepted continuous monitoring evidence, reducing audit fieldwork by 30%
  • Regulatory Changes Processed: 47 regulatory changes assessed in 2024; 12 required control updates; average time from change detection to control update: 18 days

What ships with it: 4 files

13.9 KB alongside SKILL.md, 1 of them executable

assets/

references/

scripts/

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.