Financial Regulatory Compliance Assessment
Assess financial regulatory compliance for "$ARGUMENTS". Evaluate FINRA cybersecurity requirements, SOX IT controls, and SEC reporting obligations.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"compliance-financial-compliance","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Assess) of the GRC Lifecycle workflow (compliance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or compliance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-financial-compliance","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"compliance-financial-compliance","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}.
Read .singularskills/compliance/<project>/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "". Run
/compliance-regulatory-landscape <project>first, or use--skip-checksto bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.mdfor GRC methodology reference - Read
references/assessment-template.mdfor output structure - Read
.singularskills/compliance/<project>/00-scope.mdfor scope and control framework context
- Read
Applicable regulation determination:
- Determine entity type (broker-dealer, investment adviser, public company, bank, fintech)
- Identify applicable regulations based on entity type and activities
- Assess regulatory registration status and obligations
- Document applicable regulatory landscape
FINRA compliance assessment:
- Assess cybersecurity program requirements (FINRA Rule 3110, Reg S-P, Reg S-ID)
- Evaluate record retention obligations (SEC Rule 17a-4, FINRA Rule 4511)
- Assess customer data protection and privacy (Reg S-P safeguards rule)
- Review identity theft prevention (Red Flags Rule / Reg S-ID)
- Evaluate breach reporting requirements
- Assess business continuity planning (FINRA Rule 4370)
- Review supervisory procedures for technology and cyber risks
SOX (Sarbanes-Oxley) assessment:
- Assess IT General Controls (ITGCs) for financial reporting systems
- Evaluate access controls to financial systems and data (logical access, segregation of duties)
- Review change management procedures for financial applications and infrastructure
- Assess computer operations (job scheduling, backup, batch processing)
- Evaluate audit trail integrity and log management for financial transactions
- Review IT risk assessment related to financial reporting
- Assess service organization controls (SOC 1 reports from vendors)
- Evaluate management's assessment of internal controls (Section 404)
SEC reporting requirements:
- Assess cybersecurity disclosure rules (2023) compliance
- Evaluate material incident reporting readiness (Form 8-K, 4 business days for material incidents)
- Review annual cybersecurity risk management and strategy disclosure (Form 10-K)
- Assess governance disclosure requirements (board oversight, management role)
- Evaluate materiality determination process for cyber incidents
- Review third-party risk disclosure obligations
Cross-regulation compliance:
- Identify overlapping requirements across FINRA, SOX, and SEC
- Assess unified control framework feasibility
- Map shared controls to reduce compliance burden
- Identify gaps unique to each regulation
Write the artifact to
.singularskills/compliance/<project>/01-assess/financial-compliance.mdfollowing the assessment template structure with:- Entity Classification — type, registrations, and applicable regulations
- FINRA Assessment — cybersecurity, record retention, customer protection scoring
- SOX ITGC Assessment — access controls, change management, operations, audit trail
- SEC Reporting Readiness — incident reporting, annual disclosure, governance
- Cross-Regulation Matrix — overlapping controls and unique requirements
- Evidence Inventory — existing evidence and evidence gaps
- Remediation Priorities — ranked list of gaps to address
Output
The financial regulatory compliance assessment written to .singularskills/compliance/<project>/01-assess/financial-compliance.md. Present a summary to the user highlighting:
- Applicable regulations by entity type
- Compliance score per regulatory framework (FINRA, SOX, SEC) — per framework, score = (Compliant + 0.5 × Partial) ÷ applicable requirements (N/A excluded), as a percentage
- SOX ITGC readiness level
- Top 3 gaps requiring remediation
Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"compliance-financial-compliance","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}.
Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):
---
skill: compliance-financial-compliance
workflow: compliance
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
End the artifact with ## Decisions and ## Open questions, in this shape:
## Decisions
- <what was chosen> — <why> — <what was rejected>
## Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.