Sanctions Screening
lawve-ai/awesome-legal-skills
Complete sanctions and export control analysis tool — individual designations, sectoral sanctions, dual-use goods, payment systems (SWIFT/USD), and extraterritorial regimes (EAR/ITAR/ FDPR US, ECL…
Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026).
Install Swift Csp
$ npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill swift-csp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Sushegaad/Claude-Skills-Governance-Risk-and-Compliance swift-csp --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/swift-csp/skills/swift-csp .claude/skills/swift-csp && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "swift-csp" agent skill from https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/swift-csp/skills/swift-csp into .claude/skills/swift-csp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swift-csp", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/swift-csp/skills/swift-cspType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill swift-csp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Sushegaad/Claude-Skills-Governance-Risk-and-Compliance swift-csp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/swift-csp/skills/swift-csp .agents/skills/swift-csp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "swift-csp" agent skill from https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/swift-csp/skills/swift-csp into .agents/skills/swift-csp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swift-csp", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill swift-csp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Sushegaad/Claude-Skills-Governance-Risk-and-Compliance swift-csp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/swift-csp/skills/swift-csp .cursor/skills/swift-csp && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "swift-csp" agent skill from https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/swift-csp/skills/swift-csp into .cursor/skills/swift-csp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swift-csp", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.git --path plugins/swift-csp/skills/swift-csp--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill swift-csp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Sushegaad/Claude-Skills-Governance-Risk-and-Compliance swift-csp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/swift-csp/skills/swift-csp .gemini/skills/swift-csp && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "swift-csp" agent skill from https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/swift-csp/skills/swift-csp into .gemini/skills/swift-csp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swift-csp", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Sushegaad/Claude-Skills-Governance-Risk-and-Compliance swift-cspInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill swift-csp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/swift-csp/skills/swift-csp .github/skills/swift-csp && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "swift-csp" agent skill from https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/swift-csp/skills/swift-csp into .github/skills/swift-csp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swift-csp", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill swift-csp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Sushegaad/Claude-Skills-Governance-Risk-and-Compliance swift-csp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/swift-csp/skills/swift-csp .opencode/skills/swift-csp && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "swift-csp" agent skill from https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance/tree/main/plugins/swift-csp/skills/swift-csp into .opencode/skills/swift-csp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swift-csp", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
swift-csp- GitHub stars
- 946
- Used in
- 1 other repo
- Token cost
- ~3.4k tokens
- SKILL.md length
- 1,547 words
- Files
- 3 (incl. references)
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- MIT
At a glance
Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026).
- Works in 5 steps: Map all data flows between SWIFT secure… → Implement TLS 1.2+ with… → Place all back-office connections… → …
- A user asks about SWIFT CSP
- SKILL.md covers Framework Overview, Architecture Types, The Three Security Objectives and Control Summary Table (CSCF…, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Swift Csp is an agent skill from Sushegaad/Claude-Skills-Governance-Risk-and-Compliance. Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026). Use this skill whenever a user asks about SWIFT CSP, CSCF controls, SWIFT security attestation, KYC-SA portal, SWIFT architecture types (A1/A2/A3/A4/B), mandatory vs advisory controls, independent assessment, SWIFT secure zone, secure flow zone, MFA for operators, SWIFT messaging security, payment fraud prevention on SWIFT, gap analysis for CSCF, or compliance with SWIFT's 32 controls (26…
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/swift-assessment.md` and `references/swift-controls.md`).
It sits in Mobile, covering iOS development. The repository describes itself as: Claude Skills for Governance, Risk, & Compliance (GRC): Expert-level compliance guidance for ISO 27001, SOC 2, FedRAMP, GDPR, HIPAA, NIST CSF, PCI DSS, EU AI Act, ISO 42001, ISO… The licence is MIT.
When your agent uses it
- A user asks about SWIFT CSP
- SWIFT security attestation
- SWIFT architecture types (A1/A2/A3/A4/B)
- Mandatory vs advisory controls
Example prompts
- “/swift-csp”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Map all data flows between SWIFT secure zone and back-office systems
- Implement TLS 1.2+ with certificate-based mutual authentication on all connections
- Place all back-office connections through a dedicated interface within the secure zone
- Apply firewall rules restricting back-office access to named IP addresses/ports only
- Log all back-office connection events to the SIEM
What it can do on your machine
Read from SKILL.md and the folder at commit aab13e1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Swift Csp loads about 3.4k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 208 tokens; SKILL.md has 1,547 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Sushegaad/Claude-Skills-Governance-Risk-and-Compliance at commit aab13e1, republished under its MIT licence (© Sushegaad). 1,547 words, ~3,415 tokens.
Download SKILL.mdSave it as
.claude/skills/swift-csp/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- swift-csp
- description
- Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026). Use this skill whenever a user asks about SWIFT CSP, CSCF controls, SWIFT security attestation, KYC-SA portal, SWIFT architecture types (A1/A2/A3/A4/B), mandatory vs advisory controls, independent assessment, SWIFT secure zone, secure flow zone, MFA for operators, SWIFT messaging security, payment fraud prevention on SWIFT, gap analysis for CSCF, or compliance with SWIFT's 32 controls (26 mandatory, 6 advisory in v2026) across the three objectives: Secure Your Environment, Know and Limit Access, Detect and Respond. Control 2.4 (Back-Office Data Flow Security) is now mandatory in v2026. v2026 attestation window is July 1– December 31, 2026. Trigger for any SWIFT CSP or CSCF compliance question.
SWIFT Customer Security Programme (CSP) — CSCF v2026
Last verified: 2026-09-14
You are an expert advisor on the SWIFT Customer Security Programme (CSP) and the Customer Security Controls Framework (CSCF) v2026. You help financial institutions, custodians, brokers, and service bureaux achieve and maintain mandatory compliance with SWIFT's 32 security controls across the global payment network.
Framework Overview
| Attribute | Detail |
|---|---|
| Framework name | SWIFT Customer Security Controls Framework (CSCF) |
| Current version | v2026 (effective July 2026; v2025 valid until June 2026) |
| Total controls | 32 — 26 Mandatory + 6 Advisory |
| Key v2026 change | Control 2.4 (Back-Office Data Flow Security) promoted from Advisory → Mandatory |
| Attestation | Annual — submitted via KYC Security Attestation (KYC-SA) portal |
| v2026 attestation window | July 1 – December 31, 2026 |
| Assessment type | Community-standard independent assessment (formerly self-attestation for smaller users) |
| Applies to | All SWIFT users: banks, brokers, custodians, corporates, service bureaux |
| Consequence of non-compliance | Counterparty notifications; potential suspension; regulatory escalation |
| Next version | CSCF v2027 expected to be published July 2026 |
Architecture Types
The applicable controls depend on the SWIFT connectivity architecture in use:
| Type | Description | Typical User |
|---|---|---|
| A1 | User owns BOTH the messaging interface and the communication interface on premises — the fullest local footprint | Large banks, broker-dealers |
| A2 | User owns the messaging interface; the communication interface is at a service provider | Banks splitting the stack with a provider |
| A3 | SWIFT connector on the user's premises for application-to-application connectivity (no full interfaces locally) | Mid-tier banks, asset managers |
| A4 | Customer connector — the user's own server/application connects application-to-application to a service provider's or SWIFT's services (incl. API-based connectors) | Cloud-connected FIs, API integrators |
| B | No SWIFT-specific local footprint — access via GUI/browser or fully outsourced (e.g., service bureau) | Smaller banks using bureaux |
The more SWIFT-related infrastructure you own and operate, the more controls apply.
Critical scoping step: Before assessing any control, confirm which architecture type applies — it determines which controls are mandatory, advisory, or not applicable.
The Three Security Objectives
Objective 1 — Secure Your Environment (Controls 1.x, 2.x, 3.x)
Protect the SWIFT infrastructure from external and internal threats by isolating it and reducing its attack surface.
Objective 2 — Know and Limit Access (Controls 4.x, 5.x)
Enforce strong authentication and least-privilege access to SWIFT systems and data.
Objective 3 — Detect and Respond (Controls 6.x, 7.x)
Detect anomalies, protect data integrity, and respond effectively to cyber incidents.
Control Summary Table (CSCF v2026)
⚠️ v2026 Change: Control 2.4 is now Mandatory (was Advisory in v2025). Institutions with back-office connections to SWIFT that previously skipped 2.4 must now implement it before their 2026 attestation.
| Control | Name | Status (v2026) | Objective |
|---|---|---|---|
| 1.1 | SWIFT Environment Protection | Mandatory | 1 |
| 1.2 | OS Privileged Account Control | Mandatory | 1 |
| 1.3A | Virtualisation Platform Security | Advisory | 1 |
| 1.4 | Restriction of Internet Access | Mandatory | 1 |
| 1.5A | Customer Environment Protection | Advisory | 1 |
| 2.1 | Internal Data Flow Security | Mandatory | 1 |
| 2.2 | Security Updates | Mandatory | 1 |
| 2.3 | System Hardening | Mandatory | 1 |
| 2.4 | Back-Office Data Flow Security | Mandatory (NEW in v2026 — was Advisory in v2025) | 1 |
| 2.5A | External Transmission Data Protection | Advisory | 1 |
| 2.6 | Operator Session Confidentiality and Integrity | Mandatory | 1 |
| 2.7 | Vulnerability Scanning | Mandatory | 1 |
| 2.8 | Critical Activity Outsourcing | Mandatory | 1 |
| 2.9A | Transaction Business Controls | Advisory | 1 |
| 2.10 | Application Hardening | Mandatory | 1 |
| 2.11A | RMA Business Controls | Advisory | 1 |
| 3.1 | Physical Security | Mandatory | 1 |
| 4.1 | Password Policy | Mandatory | 2 |
| 4.2 | Multi-Factor Authentication | Mandatory | 2 |
| 5.1 | Logical Access Controls | Mandatory | 2 |
| 5.2 | Token Management | Mandatory | 2 |
| 5.3A | Staffing | Advisory | 2 |
| 5.4 | Physical and Logical Password Storage | Mandatory | 2 |
| 6.1 | Malware Protection | Mandatory | 3 |
| 6.2 | Software Integrity | Mandatory | 3 |
| 6.3 | Database Integrity | Mandatory | 3 |
| 6.4 | Log and Monitoring | Mandatory | 3 |
| 6.5A | Intrusion Detection | Advisory | 3 |
| 7.1 | Cyber Incident Response Planning | Mandatory | 3 |
| 7.2 | Security Training and Awareness | Mandatory | 3 |
| 7.3A | Penetration Testing | Advisory | 3 |
| 7.4A | Scenario Risk Assessment | Advisory | 3 |
(A = Advisory control)
Control 2.4 — Back-Office Data Flow Security (Now Mandatory)
This is the most significant change in CSCF v2026. Organizations that skipped 2.4 as advisory must now implement it.
What Control 2.4 requires:
- All data flows between the SWIFT secure zone and back-office systems must be protected
- Encryption of data in transit between SWIFT and back-office (trading systems, core banking, payment hubs)
- Authentication of back-office systems connecting to the SWIFT zone
- Prevention of unauthorized data exfiltration via back-office channels
- Network segmentation between SWIFT zone and back-office environment
Common gaps when 2.4 was advisory:
- Unencrypted messaging between SWIFT Alliance and back-office payment hub
- No mutual TLS or equivalent authentication on back-office connections
- Shared network segments between SWIFT zone and general back-office VLAN
Remediation approach:
- Map all data flows between SWIFT secure zone and back-office systems
- Implement TLS 1.2+ with certificate-based mutual authentication on all connections
- Place all back-office connections through a dedicated interface within the secure zone
- Apply firewall rules restricting back-office access to named IP addresses/ports only
- Log all back-office connection events to the SIEM
Current Status — September 2026 (state where relevant)
- CSCF v2026 is the operative framework (32 controls: 26 mandatory + 6 advisory — Control 2.4 dropped its advisory-era "2.4A" suffix on promotion; 2.4 is not applicable to architecture B). v2026 also expanded mandatory assessment of customer client connectors under 14 controls (1.2, 1.3, 1.4, 2.2, 2.3, 2.6, 2.7, 3.1, 4.1, 4.2, 5.1, 5.4, 6.1, 6.4) — some architecture B users reclassify as A4. Pre-announced for v2028: protection of legacy back-office flows becomes mandatory.
- CSCF v2027: no public confirmation as of September 14, 2026 — Swift's public document centre still lists v2026 as latest (the next-year CSCF is typically released ~July via the login-gated Knowledge Centre; "v2027 readiness" webinars are running). Do not assert v2027 content; advise checking the Knowledge Centre.
- KYC-SA attestation season is decisive now: the new controls version appears in KYC-SA in early July; attest July–December, no later than December 31, and every attestation must be supported by an independent assessment (Independent Assessment Framework). Consequences of missing/non-compliant attestation: Swift reports users to their supervisor via a dedicated real-time application and status is visible to counterparties in KYC-SA (the published lever is reporting/visibility, not disconnection). Assessment capacity tightens from October — book assessors now.
Show full SKILL.md (560 more words)Show less
How to Respond
Match your output to the task type:
| Task | Output Format |
|---|---|
| Gap assessment | Table: Control ID | Control Name | Status (🔴/🟡/🟢) | Evidence Required | Gap Notes |
| Architecture scoping | Table mapping architecture type to applicable controls |
| Control deep-dive | Structured narrative: Purpose → Requirement → Implementation steps → Evidence artifacts |
| KYC-SA attestation prep | Checklist by control with attestation status and evidence pointers |
| Incident response | Step-by-step procedure with SWIFT notification obligations |
| Cross-framework mapping | Side-by-side table (CSCF ↔ ISO 27001 / PCI DSS / NIST CSF) |
| v2025 → v2026 gap | Focus specifically on Control 2.4 mandatory upgrade requirements |
Always cite the specific control number (e.g., 4.2, 6.4) — not just the control name.
Key Implementation Priorities
The following controls are the highest-risk and most commonly cited in SWIFT assessments:
- 4.2 — Multi-Factor Authentication: MFA required for all interactive operator sessions to the SWIFT environment; hardware tokens or equivalent required
- 2.4 — Back-Office Data Flow Security: Now mandatory in v2026; encrypt and authenticate all back-office connections
- 1.1 — SWIFT Environment Protection: Dedicated secure zone; no browsing from SWIFT servers; network segregation with firewall rules
- 6.4 — Log and Monitoring: All SWIFT system events and transactions logged; anomaly alerts; minimum 1-year retention
- 2.2 — Security Updates: Patches applied within 90 days for critical; emergency patches within 3 days
- 6.2 — Software Integrity: Verify integrity of SWIFT software before installation and after updates
- 2.3 — System Hardening: CIS Benchmark hardening or equivalent; remove all unnecessary services
- 1.4 — Internet Restriction: SWIFT infrastructure must not have direct internet access; jump servers required
Annual Assessment and Attestation Timeline
| Activity | Timing |
|---|---|
| v2026 attestation window opens | July 1, 2026 |
| Assessment period | July 1 – December 31, 2026 |
| KYC-SA attestation deadline | December 31, 2026 (v2026 window) |
| Counterparty visibility of attestation | Immediately upon submission |
| Non-attesting user flagged to counterparties | After deadline |
| CSCF v2027 publication expected | July 2026 |
Note: The traditional annual deadline of July 31 applied under prior cycles. For v2026, SWIFT has opened an extended attestation window (July 1 – December 31, 2026). Verify current PMO guidance at swift.com/myswift.
Common Findings and Remediation
| Control | Common Finding | Remediation |
|---|---|---|
| 2.4 | Back-office connections unencrypted or unauthenticated (now mandatory) | Implement mutual TLS 1.2+ on all back-office data flows; segment with dedicated firewall rules |
| 4.2 | Software-based OTP rather than hardware token | Deploy hardware authentication tokens for all SWIFT operators |
| 1.1 | SWIFT servers on shared network segment | Create dedicated VLAN/zone with stateful firewall rules; no dual-homing |
| 2.2 | Critical patches >90 days overdue | Establish patch management process: critical=3 days, high=90 days |
| 6.4 | Logs not reviewed; no SIEM coverage of SWIFT events | Configure SIEM to ingest Alliance Access/Gateway logs; set alert rules |
| 5.1 | Shared operator accounts; no least privilege | Enforce individual accounts; audit roles quarterly; remove stale access |
| 2.7 | Vulnerability scans not covering all SWIFT components | Include all SWIFT-connected systems in quarterly credentialed scan scope |
| 7.1 | Incident response plan not SWIFT-specific | Document SWIFT-specific IRP: detection triggers, escalation to SWIFT, evidence preservation |
| 3.1 | Server room access not logged | Implement card access with audit trail; restrict to named individuals |
Reference Files
For deeper content, read these files as needed:
- references/swift-controls.md — All 32 controls with full implementation requirements, evidence artifacts, and architecture applicability by type (A1/A2/A3/A4/B); includes v2025→v2026 change summary
- references/swift-assessment.md — KYC-SA attestation process, independent assessor requirements, cross-framework mapping (ISO 27001, PCI DSS, NIST CSF), and SWIFT-specific incident reporting obligations
This skill provides general compliance information, not legal advice. Verify current requirements against official sources; consult qualified counsel or an accredited assessor for decisions.
© Sushegaad, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in plugins/swift-csp/skills/swift-csp of Sushegaad/Claude-Skills-Governance-Risk-and-Compliance.
- SKILL.md
- references/swift-assessment.md
- references/swift-controls.md
Open the folder on GitHubat commit aab13e1
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Swift Csp next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Swift Csp this skillSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Sanctions Screeninglawve-ai/awesome-legal-skills | 847 | — | ~11k | Automated safety check: Pass | Custom licence | |
| iOS SecurityHoangNguyen0403/agent-skills-standard | 572 | — | ~500 | Automated safety check: Pass | MIT | |
| Swiftui Protwostraws/SwiftUI-Agent-Skill | 5.6k | 2 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Swiftui UI PatternsAFK-surf/OpenBridge | 430 | 4 repos | ~887 | Automated safety check: Pass | MIT | |
| Swiftui Performance Auditharperreed/dotfiles | 334 | 8 repos | ~1.4k | Automated safety check: Pass | None |
Similar skills
iOS Security
HoangNguyen0403/agent-skills-standard
Secure iOS apps with secure storage, biometrics, and data protection.
Swiftui Pro
twostraws/SwiftUI-Agent-Skill
Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance.
Swiftui UI Patterns
AFK-surf/OpenBridge
Best practices and example-driven guidance for building SwiftUI views and components.
Swiftui Performance Audit
harperreed/dotfiles
Audit and improve SwiftUI runtime performance from code review and architecture.
Swift Testing Expert
AvdLee/Swift-Testing-Agent-Skill
Expert guidance for Swift Testing: test structure, expect/require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration.
More from Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
All 34 skills in this repoEu Cra
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the…
Fedramp
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026).
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Iso42001
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert ISO 42001 AI Management System (AIMS) compliance advisor.
Nist 800 53
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
NIST SP 800-53 Rev 5 compliance advisor — all 20 control families (AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI, SR), Low/Moderate/High baseline selection, FIPS 199/200…
Related
Categories
Questions about Swift Csp
What does Swift Csp do?
Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026). Swift Csp is an agent skill from Sushegaad/Claude-Skills-Governance-Risk-and-Compliance. Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026).
When should I use Swift Csp?
Swift Csp fits situations like: A user asks about SWIFT CSP; SWIFT security attestation; SWIFT architecture types (A1/A2/A3/A4/B); mandatory vs advisory controls.
How do I install Swift Csp in Claude Code?
Run `npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill swift-csp -a claude-code`. Or copy the skill folder (plugins/swift-csp/skills/swift-csp in Sushegaad/Claude-Skills-Governance-Risk-and-Compliance) into .claude/skills/swift-csp in your project. Claude Code loads it when a task matches its description.
How do I install Swift Csp in Codex?
Run `npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill swift-csp -a codex`. Or copy the skill folder (plugins/swift-csp/skills/swift-csp in Sushegaad/Claude-Skills-Governance-Risk-and-Compliance) into .agents/skills/swift-csp in your project. Codex loads it when a task matches its description.
Can I use Swift Csp in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill swift-csp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/swift-csp, .gemini/skills/swift-csp, .github/skills/swift-csp and .opencode/skills/swift-csp in your project.
What does Swift Csp need to run?
SKILL.md names no scripts, command-line tools or credentials: Swift Csp is instructions for the agent only.
Does Swift Csp access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Swift Csp safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Swift Csp use?
Swift Csp is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Swift Csp use?
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.8k tokens, read only when the agent opens those files.
What are the alternatives to Swift Csp?
Skills that share tags, products or a category with Swift Csp: Sanctions Screening (lawve-ai/awesome-legal-skills, 847 stars), iOS Security (HoangNguyen0403/agent-skills-standard, 572 stars), Swiftui Pro (twostraws/SwiftUI-Agent-Skill, 5.6k stars) and Swiftui UI Patterns (AFK-surf/OpenBridge, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Swift Csp?
Sushegaad (a GitHub user) maintains it in Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, which has 946 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 10, 2026.
Source: Sushegaad/Claude-Skills-Governance-Risk-and-Compliance on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.