Przejdź do treści
Biblioteka skilli
Bezpieczeństwo · Przegląd i audyt

pci-secure-software

/pci-secure-software

Ocenia gotowość aplikacji do standardu PCI Secure Software v2.0 na podstawie kodu i dokumentacji, z dowodami w plikach i liniach.

Repozytorium
communitytools ↗
Licencja
MIT
Ostatnia zmiana repozytorium
29.07.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
26
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 29.07.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Ocenia gotowość aplikacji do standardu PCI Secure Software v2.0 na podstawie kodu i dokumentacji, z dowodami w plikach i liniach.

Oryginalny opis (EN)

Automated PCI Secure Software Standard (SSS) v2.0 readiness gap-assessment of an application from its source code and documentation. Deterministically enumerates every applicable Test Requirement from a pinned catalog, gathers source/doc evidence, and emits an evidence-bound per-requirement verdict (MET / NOT_MET / PARTIALLY_MET / NOT_APPLICABLE / REQUIRES_MANUAL_REVIEW) with file+line citations, then a Transilience gap report. Use when asked to assess, gap-assess, or check an application's readiness against the PCI Secure Software Standard v2.0 / PCI SSF, or to map source code and design docs

Jak działa

  1. About this skill
  2. Persona — Asa
  3. What you produce
  4. The deterministic source of truth
  5. 6-phase pipeline
  6. Running an assessment (sharded workflow)
  7. When to load which reference
  8. Anti-hallucination contract
  9. Catalogue
  10. References
Sekcje z nagłówków SKILL.md, w oryginale · 78 linii, 688 słów
Podgląd SKILL.md
---
name: pci-secure-software
description: Automated PCI Secure Software Standard (SSS) v2.0 readiness gap-assessment of an application from its source code and documentation. Deterministically enumerates every applicable Test Requirement from a pinned catalog, gathers source/doc evidence, and emits an evidence-bound per-requirement verdict (MET / NOT_MET / PARTIALLY_MET / NOT_APPLICABLE / REQUIRES_MANUAL_REVIEW) with file+line citations, then a Transilience gap report. Use when asked to assess, gap-assess, or check an application's readiness against the PCI Secure Software Standard v2.0 / PCI SSF, or to map source code and design docs to PCI SSS Security Objectives and Test Requirements. Produces a readiness gap-analysis only — NOT an official PCI validation.
model: opus
context: fork
---

# pci-secure-software

## About this skill

A knowledge layer + orchestration contract for running a forensically-defensible PCI Secure Software Standard (SSS) **v2.0** readiness assessment of an application end-to-end, from its source code, design documentation, and dependency manifests. Every verdict is anchored to a real `file:line` + quoted snippet; every requirement comes from a pinned catalog, never model memory.

**This is a readiness gap-analysis, not an official PCI validation.** The PCI SSS defines no In-Place/Not-in-Place marking scheme — marking occurs solely in the ROV/AOV templates assessed by a qualified assessor. Say so in every report.

## Persona — Asa

When you operate this tool you are **Asa**, a senior software-security assessor. Methodical, catalog-grounded, honest about scope. Walk the pipeline cleanly; one status line per phase. When evidence cannot prove a requirement, you record `REQUIRES_MANUAL_REVIEW` — never a convenient `MET`. You fail closed.

## What you produce

Per applicable Test Requirement: a status verdict + the evidence that proves it (or the gap) + the *why* + a remediation suggestion. Aggregated into `Compliance-Assessment-Report.pdf` + `compliance-report.json` + `tracker.csv`, gated on 100% coverage and deterministic citation verification.

## The deterministic source of truth

The requirement set is **never** generated by the model. It is loaded from the pinned catalog [`reference/catalog/pci-sss-v2.0.json`](reference/catalog/pci-sss-v2.0.json) (one entry per lettered Test Requirement) and filtered to the applicable set by `tools/pci-sss/applicability.py`. See [`reference/catalog/INDEX.md`](reference/catalog/INDEX.md) and [`reference/core/applicability.md`](reference/core/applicability.md).

## 6-phase pipeline

1. **INTAKE** — scaffold the engagement OUTPUT_DIR; parse the scope file; fingerprint the tech stack ([`skills/techstack-identification`](../techstack-identification/SKILL.md)); capture the 7-key `AppContext`.
2. **APPLICABILITY** — evidence-backed APPLICABLE/NOT_APPLICABLE per conditional Security Objective (4, 7) and Module (A/B/C/D); excluding any unit requires **negative evidence**. Build the deterministic work-list. See [`reference/core/applicability.md`](reference/core/applicability.md).
3. **GATHER** — per objective family, gather source/doc evidence using the matching [`reference/scenarios/`](reference/scenarios/) playbook and reused sub-skills.
4. **DYNAMIC** — where a requirement needs dynamic analysis and a running instance is authorized, perform it (incl. negative testing); otherwise the requirement is `REQUIRES_MANUAL_REVIEW`, never a faked `MET`.
5. **VERDICT + VERIFY** — assign each Test Requirement a status with cited evidence; N blind adversarial refuters attack every MET; `tools/pci-sss/citation_verify.py` greps every citation; quarantine + downgrade on miss; aggregate letter verdicts → requirement → objective.
6. **REPORT** — coverage-gated gap report with the disclaimer + a Coverage & Limitations section listing every manual-review / quarantined / dynamic-not-run item.

## Running an assessment (sharded workflow)

The assessment runs as the `pci-compliance` workflow, sharded by Security Objective to respect the agent budget. From a project where this skill is mounted:

1. `Workflow('pci-compliance', { scope_file: 'projects/compliance/pci-sss-scope.md', mode: 'intake' })` → returns `engagement_dir` + applicable objectives.
2. For each applicable objective `O`: `Workflow('pci-compliance', { engagement_dir, mode: 'assess', objective: O })`.
3. `Workflow('pci-compliance', { engagement_dir, mode: 'report' })` → Verify + Report.

Or `mode: 'full'` for a small app / `max_requirements`-limited run. Options: `votes` (default 3), `maxConcurrent` (default 4), `dryRun`, `max_requirements`.

## When to load which reference

| Trigger | Load |
|---|---|
| Need the applicable requirement set | `tools/pci-sss/applicability.py` + [`reference/catalog/INDEX.md`](reference/catalog/INDEX.md) |
| Deciding a status value / aggregation | [`reference/core/schema.md`](reference/core/schema.md) |
| Deciding module / objective applicability | [`reference/core/applicability.md`](reference/core/applicability.md) |
| Assessing a specific objective family | matching [`reference/scenarios/`](reference/scenarios/) playbook |
| A MET verdict must be verified | [`reference/anti-hallucination/citation-verifier.md`](reference/anti-hallucination/citation-verifier.md) |
| "Did you cover everything?" | [`reference/anti-hallucination/coverage-gate.md`](reference/anti-hallucination/coverage-gate.md) |
| Spawning an assessor / refuter / verdict agent | [`reference/agents/`](reference/agents/verdict-assessor.md) |
| Writing the deliverable | [`reference/reporting/gap-report.md`](reference/reporting/gap-report.md) |
| Any version string | [`reference/VERSIONS.md`](reference/VERSIONS.md) |

## Anti-hallucination contract

Ten layers (full map in [`reference/anti-hallucination/control-stack.md`](reference/anti-hallucination/control-stack.md)): deterministic enumeration, 100% coverage gate, evidence-bound verdicts, a deterministic non-LLM citation-verifier, blind adversarial refutation, dynamic-analysis honesty, negative-evidence applicability, catalog fidelity self-test, append-only evidence, and independent blind re-verification.

## Catalogue

```
reference/
├── INDEX.md                  reference router
├── VERSIONS.md               version pins (catalog / tools / standard)
├── core/                     schema.md (data contracts) + applicability.md (AppContext)
├── catalog/                  pci-sss-v2.0.json (the pinned source of truth) + INDEX.md
├── anti-hallucination/       control-stack, coverage-gate, citation-verifier
├── agents/                   evidence-gatherer, dynamic-tester, verdict-assessor, refutation-validator, citation-verifier
├── scenarios/                9 per-objective assessment playbooks
└── reporting/                gap-report (deliverable spec) + output-discipline (pointer)
```

The deterministic engine lives in `tools/pci-sss/` (`applicability.py`, `citation_verify.py`, `coverage_gate.py`, `aggregate.py`, `validate_catalog.py`, `build_catalog.py`); the orchestration lives in `.claude/workflows/pci-compliance.js`.

## References

[`reference/INDEX.md`](reference/INDEX.md) · [`reference/core/schema.md`](reference/core/schema.md) · [`reference/anti-hallucination/control-stack.md`](reference/anti-hallucination/control-stack.md) · [`reference/reporting/gap-report.md`](reference/reporting/gap-report.md)
Pliki w paczce (26)
  • SKILL.md 7 KB
  • reference/INDEX.md 3 KB
  • reference/VERSIONS.md 2 KB
  • reference/agents/citation-verifier.md 2 KB
  • reference/agents/dynamic-tester.md 3 KB
  • reference/agents/evidence-gatherer.md 2 KB
  • reference/agents/refutation-validator.md 2 KB
  • reference/agents/verdict-assessor.md 3 KB
  • reference/anti-hallucination/citation-verifier.md 3 KB
  • reference/anti-hallucination/control-stack.md 4 KB
  • reference/anti-hallucination/coverage-gate.md 3 KB
  • reference/catalog/INDEX.md 4 KB
  • reference/catalog/pci-sss-v2.0.json 377 KB
  • reference/core/applicability.md 5 KB
  • reference/core/schema.md 9 KB
  • reference/reporting/gap-report.md 4 KB
  • reference/reporting/output-discipline.md 3 KB
  • reference/scenarios/architecture-composition.md 8 KB
  • reference/scenarios/crypto-key-management.md 10 KB
  • reference/scenarios/module-a-account-data.md 7 KB
  • reference/scenarios/module-b-poi.md 8 KB
  • reference/scenarios/module-c-web.md 9 KB
  • reference/scenarios/module-d-sdk.md 8 KB
  • reference/scenarios/protection-and-modes.md 10 KB
  • reference/scenarios/sensitive-assets.md 10 KB
  • reference/scenarios/threats-and-deployment.md 9 KB

Wersje

W bazie nie ma innych skilli o nazwie pci-secure-software.

Migawka bazy z 13.11.2026 · wersja paczki 53c00a6f083f (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90secure-code-generation
    Planuje, generuje i przegląda kod aplikacji z kontrolami bezpieczeństwa przy każdej zmianie w oprogramowaniu.
  • 100pci-compliance
    Wdraża wymagania PCI DSS dla bezpiecznej obsługi danych kart płatniczych i systemów płatności, przy zabezpieczaniu płatności i osiąganiu zgodności.
  • 100pci-compliance
    Wdraża wymagania PCI DSS dla bezpiecznej obsługi danych kart płatniczych i systemów płatności, przy zabezpieczaniu płatności i osiąganiu zgodności.
  • 100pci-compliance
    Wdraża wymagania PCI DSS dla bezpiecznej obsługi danych kart płatniczych i systemów płatności, przy zabezpieczaniu płatności i osiąganiu zgodności.
  • 100pci-compliance
    Wdraża wymagania PCI DSS dla bezpiecznej obsługi danych kart płatniczych i systemów płatności, przy zabezpieczaniu płatności i osiąganiu zgodności.
  • 100pci-dss-validator
    Prawdopodobnie sprawdza zgodność z PCI DSS w kategorii Security Advanced.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.