Sushegaad/Claude-Skills-Governance-Risk-and-Compliance / plugins/sox-itgc/skills/sox-itgc
sox-itgc
VerifiedExpert SOX IT General Controls (ITGC) advisor for finance, internal audit and IT compliance teams. Covers the four ITGC domains external auditors test for SOX 404 - access to programs and data, program changes, computer operations, and program development - plus scoping in-scope systems from the financial statements, designing risk-and-control matrices (RCMs), writing control narratives and test scripts, evaluating deficiencies (control deficiency vs significant deficiency vs material weakness under AS 2201 and Reg S-X), drafting remediation plans, SOX 404(a)/404(b) applicability and filer status, IPO readiness timelines, and COSO 2013 alignment. Use this skill whenever a user mentions SOX, ITGC, IT general controls, 404(a)/404(b), ICFR, material weakness, user access reviews, segregation of duties in IT, change management controls for financial systems, SOX testing or walkthroughs, PCAOB audits, or quarterly compliance for financial reporting systems.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.5 KB |
| references/deficiency-evaluation.md | markdown | 3.9 KB |
| references/itgc-control-catalog.md | markdown | 4.5 KB |
| references/scoping-and-rcm.md | markdown | 3.3 KB |
references/itgc-control-catalog.md
View on GitHub# ITGC Control Catalog — Controls, Tests, Evidence
Cadences and sample sizes below are prevailing audit convention (no SEC/PCAOB rule prescribes them); align final figures with the external auditor.
## Domain 1 — Access to Programs and Data
| Control | Test procedure | Evidence |
|---|---|---|
| New/modified access granted on documented, role-appropriate approval | Sample new hires/transfers → trace ticket → approval → granted rights match request | Access request tickets, approval trail, system rights report |
| Terminations deprovisioned timely (24–72h convention) | Full population: HR term list vs system disable dates; test exceptions | HR extract, disable timestamps, exception analysis |
| Quarterly user access reviews (UARs) for in-scope systems | Sample quarters → completeness of population, reviewer independence, evidence of revocations executed | UAR workbooks, sign-offs, revocation tickets |
| Privileged access restricted and monitored | Enumerate admin/superuser (incl. DB sysadmin, OS root, ERP profiles like SAP_ALL); justify each; review monitoring/vault logs | Privileged account inventory, PAM logs, justification matrix |
| SoD within access design | Test rule set for conflicting duties (e.g., create vendor + pay vendor; develop + deploy) | SoD ruleset, conflict report, mitigations |
| Authentication policy enforced (incl. MFA where deployed) | Inspect configuration vs policy; test service/generic accounts ownership and password vaulting | Config screenshots, service account register |
| Direct data access (DB/OS) restricted | Enumerate direct-write access to financial data outside the application | DB permission listings, firefighter/elevated-access logs |
## Domain 2 — Program Changes
| Control | Test procedure | Evidence |
|---|---|---|
| Changes approved before production migration | Sample changes (25 convention for frequent) → approval precedes migration date | Change tickets, CAB minutes, deployment logs |
| Testing performed and documented before migration | Same sample → test plans/results/UAT sign-off | Test evidence attached to ticket |
| Developer/deployer segregation | Compare developer list to production-migration rights; where tooling merges roles, test compensating review | Access listings for deploy tooling, pipeline permissions |
| Emergency changes controlled | Sample emergency changes → expedited authorization + after-the-fact approval and review | Emergency change log, post-implementation reviews |
| Configuration changes in scope | Confirm change population includes config/master-data-engine/workflow changes, not just code | Population completeness reconciliation (tool extract vs deployment log) |
## Domain 3 — Computer Operations
| Control | Test procedure | Evidence |
|---|---|---|
| Financially relevant batch jobs scheduled and monitored; failures resolved | Sample days/failures → alert → ticket → resolution → rerun evidence | Scheduler logs, incident tickets |
| Backups executed and monitored | Sample periods → completion logs, failure follow-up | Backup reports, failure tickets |
| Restore testing performed periodically | Inspect most recent restore test for in-scope systems | Restore test results |
| Incidents affecting financial systems managed | Sample incidents → triage, resolution, escalation to finance where data integrity implicated | Incident records |
## Domain 4 — Program Development
| Control | Test procedure | Evidence |
|---|---|---|
| New system/major implementation authorized | Project charter/steering approval | Charter, minutes |
| Testing strategy incl. UAT with business sign-off | Inspect test phases and finance sign-off before go-live | UAT results, sign-off |
| Data conversion validated | Reconciliations of converted balances; error handling | Conversion recs, sign-off |
| Go-live approval and hypercare | Cutover approval; post-go-live issue tracking | Go-live approval, hypercare log |
## Cross-cutting
- **IPE (information produced by the entity)**: any report used in a control needs accuracy/completeness validation (source, parameters, logic).
- **End-user computing**: in-scope spreadsheets need access restriction, input control, and change/version protection proportional to complexity.
- **SOC 1 reliance**: map subservice CUECs into your control set; verify the report period covers your fiscal year; bridge letters for gaps.
- **AI/automation (emerging)**: model/prompt/config changes to automated financial controls follow Domain 2; monitor PCAOB focus on GenAI at issuers (2025 priorities).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |