Command
research
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
@grcengclubView CommandSecurity
Command
/assess
APRA CPS 234 compliance gap assessment
Install
> /plugin marketplace add GRCEngClub/claude-grc-engineeringHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/assess
Context preview
What this command does when you run it.
APRA CPS 234 compliance gap assessment
Command definition
assess.mddescription: APRA CPS 234 compliance gap assessment
APRA CPS 234 Assessment
Runs a compliance gap assessment against APRA Prudential Standard CPS 234 Information Security by delegating to `/grc-engineer:gap-assessment` with the framework's SCF identifier, then overlays CPS 234-specific context and evidence requirements.
Usage
/au-apra-cps-234:assess [--scope=<scope>] [--sources=<connector-list>]
Arguments
- `--scope=<scope>` (optional) - narrow the assessment to a CPS 234 workstream
such as `asset-ownership`, `information-security-capability`, `control-testing`, `incident-management`, `third-party-reliance`, or `board-reporting`.
- `--sources=<connector-list>` (optional) - comma-separated connector plugins.
What the assessment produces
1. **Compliance score** - overall CPS 234 readiness percentage, weighted by mapped SCF controls. 2. **Applicable-requirements summary** - which CPS 234 expectations apply to the organization. 3. **Control-by-control gap** - all 38 mapped controls, with pass/fail/inconclusive status from connector findings. 4. **Evidence gaps** - controls where no evidence source is configured. 5. **Remediation roadmap** - prioritized by severity and effort.
Delegation
Under the hood:
/grc-engineer:gap-assessment "apac-aus-ps-cps-234-2019" [--sources=<connector-list>]
The SCF crosswalk expands 52 SCF controls into the 38 CPS 234 mapped controls.
Framework-specific notes
- Start with `/au-apra-cps-234:scope` to identify whether the entity is
APRA-regulated and which information assets are managed directly, by related parties, or by third parties.
- Common assessment scopes are information asset ownership, control design,
control testing, material incident readiness, third-party assurance, and board or senior management reporting.
- For ISO 27001, SOC 2, or Essential Eight programs, verify that evidence maps
to CPS 234's prudential language: capability, threats, vulnerabilities, criticality, sensitivity, testing, and APRA notification.
- Treat third-party and cloud evidence as in scope when those providers manage
information assets for the regulated entity.
Read more
description: APRA CPS 234 compliance gap assessment
APRA CPS 234 Assessment
Runs a compliance gap assessment against APRA Prudential Standard CPS 234 Information Security by delegating to `/grc-engineer:gap-assessment` with the framework's SCF identifier, then overlays CPS 234-specific context and evidence requirements.
Usage
/au-apra-cps-234:assess [--scope=<scope>] [--sources=<connector-list>]
Arguments
- `--scope=<scope>` (optional) - narrow the assessment to a CPS 234 workstream
such as `asset-ownership`, `information-security-capability`, `control-testing`, `incident-management`, `third-party-reliance`, or `board-reporting`.
- `--sources=<connector-list>` (optional) - comma-separated connector plugins.
What the assessment produces
1. **Compliance score** - overall CPS 234 readiness percentage, weighted by mapped SCF controls. 2. **Applicable-requirements summary** - which CPS 234 expectations apply to the organization. 3. **Control-by-control gap** - all 38 mapped controls, with pass/fail/inconclusive status from connector findings. 4. **Evidence gaps** - controls where no evidence source is configured. 5. **Remediation roadmap** - prioritized by severity and effort.
Delegation
Under the hood:
/grc-engineer:gap-assessment "apac-aus-ps-cps-234-2019" [--sources=<connector-list>]
The SCF crosswalk expands 52 SCF controls into the 38 CPS 234 mapped controls.
Framework-specific notes
- Start with `/au-apra-cps-234:scope` to identify whether the entity is
APRA-regulated and which information assets are managed directly, by related parties, or by third parties.
- Common assessment scopes are information asset ownership, control design,
control testing, material incident readiness, third-party assurance, and board or senior management reporting.
- For ISO 27001, SOC 2, or Essential Eight programs, verify that evidence maps
to CPS 234's prudential language: capability, threats, vulnerabilities, criticality, sensitivity, testing, and APRA notification.
- Treat third-party and cloud evidence as in scope when those providers manage
information assets for the regulated entity.
Ships withtrust-center
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Get the whole plugin
Stats
398
Stars
90
Forks
Active
Maintenance
JavaScript
Language
8d ago
Last commit
8mo ago
Created
Repo: GRCEngClub/claude-grc-engineering
Other commands on trust-center.
@grcengclubView CommandCommand
collect
Query AWS for compliance-relevant configuration across IAM, S3, CloudTrail, EBS, and emit findings conforming to the v1 contract.
@grcengclubView CommandCommand
setup
Install the frdocx-to-froscal-ssp Python pipeline and verify its dependencies. Idempotent.
@grcengclubView CommandCommand
Command
retrieve
Retrieve a single AWS Secrets Manager secret value to stdout or a 0600-permission file. Opt-in retrieval mode — never writes to the findings cache.
@grcengclubView CommandCommand
scan
Run testssl.sh against one or more HTTPS endpoints and emit v1 Findings mapped to SOC 2, NIST 800-53, PCI DSS 4.0.1, ISO 27001, and SCF controls.
@grcengclubView Command