Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Senior Secops

  • 849 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

senior-secops is a Claude Code skill that references SOC 2, PCI-DSS, HIPAA, and GDPR control requirements for developers who must harden production systems or prepare compliance audits.

About

senior-secops is a compliance reference skill covering SOC 2 Type II trust service criteria, PCI-DSS, HIPAA, and GDPR requirements with control tables, automation guidance, and audit preparation workflows. The skill maps security, availability, processing integrity, and privacy obligations to concrete controls such as access management, encryption, monitoring, disaster recovery, and audit logging. Developers reach for senior-secops when scoping SOC 2 evidence, validating PCI cardholder environments, reviewing HIPAA safeguards, or documenting GDPR data-processing obligations before an external audit or production hardening sprint. The readme organizes four major regulatory frameworks plus dedicated sections on compliance automation and audit preparation.

  • Complete SOC 2 Type II Trust Services Criteria reference with 5 core categories
  • Security Controls Checklist covering CC1 through CC3 with 20+ verifiable items
  • Dedicated sections for PCI-DSS, HIPAA, and GDPR requirements
  • Compliance Automation and Audit Preparation guidance
  • Ready-to-use markdown checklists for evidence collection

Senior Secops by the numbers

  • 849 all-time installs (skills.sh)
  • +6 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #411 of 2,203 Security skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill senior-secops

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs849
repo stars23.5k
Security audit2 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you map SOC 2 controls to production systems?

Reference exact SOC 2, PCI-DSS, HIPAA, and GDPR controls while preparing for audits or hardening production systems.

Who is it for?

Security engineers and backend leads responsible for compliance audits, regulated data, or production hardening across SaaS and API services.

Skip if: Developers who only need application-level OWASP fixes without regulatory frameworks or formal audit evidence requirements.

When should I use this skill?

A developer asks about SOC 2 trust criteria, PCI-DSS scope, HIPAA safeguards, GDPR obligations, or audit preparation controls.

What you get

Control matrices, audit checklists, and hardening recommendations aligned to SOC 2, PCI-DSS, HIPAA, and GDPR.

  • control matrices
  • audit checklists
  • hardening recommendations

By the numbers

  • Covers 4 compliance frameworks: SOC 2, PCI-DSS, HIPAA, and GDPR

Files

SKILL.mdMarkdownGitHub ↗

Senior SecOps Engineer

Complete toolkit for Security Operations including vulnerability management, compliance verification, secure coding practices, and security automation.

---

Table of Contents

---

Core Capabilities

1. Security Scanner

Scan source code for security vulnerabilities including hardcoded secrets, SQL injection, XSS, command injection, and path traversal.

# Scan project for security issues
python scripts/security_scanner.py /path/to/project

# Filter by severity
python scripts/security_scanner.py /path/to/project --severity high

# JSON output for CI/CD
python scripts/security_scanner.py /path/to/project --json --output report.json

Detects:

  • Hardcoded secrets (API keys, passwords, AWS credentials, GitHub tokens, private keys)
  • SQL injection patterns (string concatenation, f-strings, template literals)
  • XSS vulnerabilities (innerHTML assignment, unsafe DOM manipulation, React unsafe patterns)
  • Command injection (shell=True, exec, eval with user input)
  • Path traversal (file operations with user input)

2. Vulnerability Assessor

Scan dependencies for known CVEs across npm, Python, and Go ecosystems.

# Assess project dependencies
python scripts/vulnerability_assessor.py /path/to/project

# Critical/high only
python scripts/vulnerability_assessor.py /path/to/project --severity high

# Export vulnerability report
python scripts/vulnerability_assessor.py /path/to/project --json --output vulns.json

Scans:

  • package.json and package-lock.json (npm)
  • requirements.txt and pyproject.toml (Python)
  • go.mod (Go)

Output:

  • CVE IDs with CVSS scores
  • Affected package versions
  • Fixed versions for remediation
  • Overall risk score (0-100)

3. Compliance Checker

Verify security compliance against SOC 2, PCI-DSS, HIPAA, and GDPR frameworks.

# Check all frameworks
python scripts/compliance_checker.py /path/to/project

# Specific framework
python scripts/compliance_checker.py /path/to/project --framework soc2
python scripts/compliance_checker.py /path/to/project --framework pci-dss
python scripts/compliance_checker.py /path/to/project --framework hipaa
python scripts/compliance_checker.py /path/to/project --framework gdpr

# Export compliance report
python scripts/compliance_checker.py /path/to/project --json --output compliance.json

Verifies:

  • Access control implementation
  • Encryption at rest and in transit
  • Audit logging
  • Authentication strength (MFA, password hashing)
  • Security documentation
  • CI/CD security controls

---

Workflows

Workflow 1: Security Audit

Complete security assessment of a codebase.

# Step 1: Scan for code vulnerabilities
python scripts/security_scanner.py . --severity medium
# STOP if exit code 2 — resolve critical findings before continuing
# Step 2: Check dependency vulnerabilities
python scripts/vulnerability_assessor.py . --severity high
# STOP if exit code 2 — patch critical CVEs before continuing
# Step 3: Verify compliance controls
python scripts/compliance_checker.py . --framework all
# STOP if exit code 2 — address critical gaps before proceeding
# Step 4: Generate combined reports
python scripts/security_scanner.py . --json --output security.json
python scripts/vulnerability_assessor.py . --json --output vulns.json
python scripts/compliance_checker.py . --json --output compliance.json

Workflow 2: CI/CD Security Gate

Integrate security checks into deployment pipeline.

# .github/workflows/security.yml
name: "security-scan"

on:
  pull_request:
    branches: [main, develop]

jobs:
  security-scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: "set-up-python"
        uses: actions/setup-python@v5
        with:
          python-version: '3.11'

      - name: "security-scanner"
        run: python scripts/security_scanner.py . --severity high

      - name: "vulnerability-assessment"
        run: python scripts/vulnerability_assessor.py . --severity critical

      - name: "compliance-check"
        run: python scripts/compliance_checker.py . --framework soc2

Each step fails the pipeline on its respective exit code — no deployment proceeds past a critical finding.

Workflow 3: CVE Triage

Respond to a new CVE affecting your application.

1. ASSESS (0-2 hours)
   - Identify affected systems using vulnerability_assessor.py
   - Check if CVE is being actively exploited
   - Determine CVSS environmental score for your context
   - STOP if CVSS 9.0+ on internet-facing system — escalate immediately

2. PRIORITIZE
   - Critical (CVSS 9.0+, internet-facing): 24 hours
   - High (CVSS 7.0-8.9): 7 days
   - Medium (CVSS 4.0-6.9): 30 days
   - Low (CVSS < 4.0): 90 days

3. REMEDIATE
   - Update affected dependency to fixed version
   - Run security_scanner.py to verify fix (must return exit code 0)
   - STOP if scanner still flags the CVE — do not deploy
   - Test for regressions
   - Deploy with enhanced monitoring

4. VERIFY
   - Re-run vulnerability_assessor.py
   - Confirm CVE no longer reported
   - Document remediation actions

Workflow 4: Incident Response

Security incident handling procedure.

PHASE 1: DETECT & IDENTIFY (0-15 min)
- Alert received and acknowledged
- Initial severity assessment (SEV-1 to SEV-4)
- Incident commander assigned
- Communication channel established

PHASE 2: CONTAIN (15-60 min)
- Affected systems identified
- Network isolation if needed
- Credentials rotated if compromised
- Preserve evidence (logs, memory dumps)

PHASE 3: ERADICATE (1-4 hours)
- Root cause identified
- Malware/backdoors removed
- Vulnerabilities patched (run security_scanner.py; must return exit code 0)
- Systems hardened

PHASE 4: RECOVER (4-24 hours)
- Systems restored from clean backup
- Services brought back online
- Enhanced monitoring enabled
- User access restored

PHASE 5: POST-INCIDENT (24-72 hours)
- Incident timeline documented
- Root cause analysis complete
- Lessons learned documented
- Preventive measures implemented
- Stakeholder report delivered

---

Tool Reference

security_scanner.py

OptionDescription
targetDirectory or file to scan
--severity, -sMinimum severity: critical, high, medium, low
--verbose, -vShow files as they're scanned
--jsonOutput results as JSON
--output, -oWrite results to file

Exit Codes: 0 = no critical/high findings · 1 = high severity findings · 2 = critical severity findings

vulnerability_assessor.py

OptionDescription
targetDirectory containing dependency files
--severity, -sMinimum severity: critical, high, medium, low
--verbose, -vShow files as they're scanned
--jsonOutput results as JSON
--output, -oWrite results to file

Exit Codes: 0 = no critical/high vulnerabilities · 1 = high severity vulnerabilities · 2 = critical severity vulnerabilities

compliance_checker.py

OptionDescription
targetDirectory to check
--framework, -fFramework: soc2, pci-dss, hipaa, gdpr, all
--verbose, -vShow checks as they run
--jsonOutput results as JSON
--output, -oWrite results to file

Exit Codes: 0 = compliant (90%+ score) · 1 = non-compliant (50-69% score) · 2 = critical gaps (<50% score)

---

Security Standards

See references/security_standards.md for OWASP Top 10 full guidance, secure coding standards, authentication requirements, and API security controls.

Secure Coding Checklist

## Input Validation
- [ ] Validate all input on server side
- [ ] Use allowlists over denylists
- [ ] Sanitize for specific context (HTML, SQL, shell)

## Output Encoding
- [ ] HTML encode for browser output
- [ ] URL encode for URLs
- [ ] JavaScript encode for script contexts

## Authentication
- [ ] Use bcrypt/argon2 for passwords
- [ ] Implement MFA for sensitive operations
- [ ] Enforce strong password policy

## Session Management
- [ ] Generate secure random session IDs
- [ ] Set HttpOnly, Secure, SameSite flags
- [ ] Implement session timeout (15 min idle)

## Error Handling
- [ ] Log errors with context (no secrets)
- [ ] Return generic messages to users
- [ ] Never expose stack traces in production

## Secrets Management
- [ ] Use environment variables or secrets manager
- [ ] Never commit secrets to version control
- [ ] Rotate credentials regularly

---

Compliance Frameworks

See references/compliance_requirements.md for full control mappings. Run compliance_checker.py to verify the controls below:

SOC 2 Type II

  • CC6 Logical Access: authentication, authorization, MFA
  • CC7 System Operations: monitoring, logging, incident response
  • CC8 Change Management: CI/CD, code review, deployment controls

PCI-DSS v4.0

  • Req 3/4: Encryption at rest and in transit (TLS 1.2+)
  • Req 6: Secure development (input validation, secure coding)
  • Req 8: Strong authentication (MFA, password policy)
  • Req 10/11: Audit logging, SAST/DAST/penetration testing

HIPAA Security Rule

  • Unique user IDs and audit trails for PHI access (164.312(a)(1), 164.312(b))
  • MFA for person/entity authentication (164.312(d))
  • Transmission encryption via TLS (164.312(e)(1))

GDPR

  • Art 25/32: Privacy by design, encryption, pseudonymization
  • Art 33: Breach notification within 72 hours
  • Art 17/20: Right to erasure and data portability

---

Best Practices

Secrets Management

# BAD: Hardcoded secret
API_KEY = "sk-1234567890abcdef"

# GOOD: Environment variable
import os
API_KEY = os.environ.get("API_KEY")

# BETTER: Secrets manager
from your_vault_client import get_secret
API_KEY = get_secret("api/key")

SQL Injection Prevention

# BAD: String concatenation
query = f"SELECT * FROM users WHERE id = {user_id}"

# GOOD: Parameterized query
cursor.execute("SELECT * FROM users WHERE id = %s", (user_id,))

XSS Prevention

// BAD: Direct innerHTML assignment is vulnerable
// GOOD: Use textContent (auto-escaped)
element.textContent = userInput;

// GOOD: Use sanitization library for HTML
import DOMPurify from 'dompurify';
const safeHTML = DOMPurify.sanitize(userInput);

Authentication

// Password hashing
const bcrypt = require('bcrypt');
const SALT_ROUNDS = 12;

// Hash password
const hash = await bcrypt.hash(password, SALT_ROUNDS);

// Verify password
const match = await bcrypt.compare(password, hash);

Security Headers

// Express.js security headers
const helmet = require('helmet');
app.use(helmet());

// Or manually set headers:
app.use((req, res, next) => {
  res.setHeader('X-Content-Type-Options', 'nosniff');
  res.setHeader('X-Frame-Options', 'DENY');
  res.setHeader('X-XSS-Protection', '1; mode=block');
  res.setHeader('Strict-Transport-Security', 'max-age=31536000; includeSubDomains');
  res.setHeader('Content-Security-Policy', "default-src 'self'");
  next();
});

---

OWASP Top 10 Quick-Check

Rapid 15-minute assessment — run through each category and note pass/fail. For deep-dive testing, hand off to the security-pen-testing skill.

#CategoryOne-Line Check
A01Broken Access ControlVerify role checks on every endpoint; test horizontal privilege escalation
A02Cryptographic FailuresConfirm TLS 1.2+ everywhere; no secrets in logs or source
A03InjectionRun parameterized query audit; check ORM raw-query usage
A04Insecure DesignReview threat model exists for critical flows
A05Security MisconfigurationCheck default credentials removed; error pages generic
A06Vulnerable ComponentsRun vulnerability_assessor.py; zero critical/high CVEs
A07Auth FailuresVerify MFA on admin; brute-force protection active
A08Software & Data IntegrityConfirm CI/CD pipeline signs artifacts; no unsigned deps
A09Logging & MonitoringValidate audit logs capture auth events; alerts configured
A10SSRFTest internal URL filters; block metadata endpoints (169.254.169.254)
Deep dive needed? Hand off to security-pen-testing for full OWASP Testing Guide coverage.

---

Secret Scanning Tools

Choose the right scanner for each stage of your workflow:

ToolBest ForLanguagePre-commitCI/CDCustom Rules
gitleaksCI pipelines, full-repo scansGoYesYesTOML regexes
detect-secretsPre-commit hooks, incrementalPythonYesPartialPlugin-based
truffleHogDeep history scans, entropyGoNoYesRegex + entropy

Recommended setup: Use detect-secrets as a pre-commit hook (catches secrets before they enter history) and gitleaks in CI (catches anything that slips through).

# detect-secrets pre-commit hook (.pre-commit-config.yaml)
- repo: https://github.com/Yelp/detect-secrets
  rev: v1.4.0
  hooks:
    - id: detect-secrets
      args: ['--baseline', '.secrets.baseline']

# gitleaks in GitHub Actions
- name: gitleaks
  uses: gitleaks/gitleaks-action@v2
  env:
    GITLEAKS_LICENSE: ${{ secrets.GITLEAKS_LICENSE }}

---

Supply Chain Security

Protect against dependency and artifact tampering with SBOM generation, artifact signing, and SLSA compliance.

SBOM Generation:

  • syft — generates SBOMs from container images or source dirs (SPDX, CycloneDX formats)
  • cyclonedx-cli — CycloneDX-native tooling; merge multiple SBOMs for mono-repos
# Generate SBOM from container image
syft packages ghcr.io/org/app:latest -o cyclonedx-json > sbom.json

Artifact Signing (Sigstore/cosign):

# Sign a container image (keyless via OIDC)
cosign sign ghcr.io/org/app:latest
# Verify signature
cosign verify ghcr.io/org/app:latest --certificate-identity=ci@org.com --certificate-oidc-issuer=https://token.actions.githubusercontent.com

SLSA Levels Overview:

LevelRequirementWhat It Proves
1Build process documentedProvenance exists
2Hosted build service, signed provenanceTamper-resistant provenance
3Hardened build platform, non-falsifiable provenanceTamper-proof build
4Two-party review, hermetic buildsMaximum supply-chain assurance
Cross-references: security-pen-testing (vulnerability exploitation testing), dependency-auditor (license and CVE audit for dependencies).

---

Reference Documentation

DocumentDescription
references/security_standards.mdOWASP Top 10, secure coding, authentication, API security
references/vulnerability_management_guide.mdCVE triage, CVSS scoring, remediation workflows
references/compliance_requirements.mdSOC 2, PCI-DSS, HIPAA, GDPR full control mappings

Related skills

How it compares

Choose senior-secops over generic security linters when the task requires mapping controls to formal audit frameworks rather than fixing individual code vulnerabilities.

FAQ

Which compliance frameworks does senior-secops cover?

senior-secops covers SOC 2 Type II, PCI-DSS, HIPAA, and GDPR. The readme includes trust service criteria tables, framework-specific controls, compliance automation guidance, and audit preparation steps for each.

When should a developer invoke senior-secops?

senior-secops fits audit preparation, production hardening, and control-gap analysis for regulated workloads. Use it when mapping encryption, access controls, monitoring, or disaster recovery to formal compliance requirements.

Is Senior Secops safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Securityauditcomplianceappsec

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.