/scope
Determine whether APRA CPS 234 applies to the organization
$ npx -y skills add GRCEngClub/claude-grc-engineering --agent claude-codeHow 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
/scope
Context preview
What this command does when you run it.
Determine whether APRA CPS 234 applies to the organization
Command definition
scope.mddescription: Determine whether APRA CPS 234 applies to the organization
APRA CPS 234 Scope
Determines whether and how APRA Prudential Standard CPS 234 Information Security applies to the organization. Reference-depth scope is a decision-tree prompt; Full-depth plugins extend this with entity- and asset-aware logic.
Usage
/au-apra-cps-234:scope
What this produces
- **Applicability verdict**: in-scope, out-of-scope, or partially in-scope.
- **In-scope entity types**: APRA-regulated entity, RSE licensee, insurer,
authorised deposit-taking institution, related party, or third-party service provider supporting regulated operations.
- **In-scope assets**: information assets classified by sensitivity,
criticality, owner, hosting model, and dependency.
- **Jurisdiction reach**: APRA-regulated Australian operations and supporting
offshore, cloud, related-party, or outsourced services.
- **Next steps**: whether to proceed with `/au-apra-cps-234:assess` or
`/au-apra-cps-234:evidence-checklist`.
Framework-specific scope triggers
Ask the minimum questions needed to classify CPS 234 applicability:
- Is the organization an APRA-regulated entity or part of a regulated group?
- Does it manage information assets for an APRA-regulated entity?
- Which information assets are critical or sensitive?
- Which assets are managed by related parties, outsourced providers, cloud
services, or offshore teams?
- Who owns each information asset and who is accountable for control design,
control testing, and incident escalation?
- Are there materiality thresholds for information security incidents and
control weaknesses?
- Are control testing results, third-party assurance, and incident exercises
reported to board or senior management?
Return an applicability verdict, in-scope assets, accountable owners, and the follow-up command that should run next. Do not ask users to search CPS 234; translate their answers into practical scoping outcomes.
Read more
description: Determine whether APRA CPS 234 applies to the organization
APRA CPS 234 Scope
Determines whether and how APRA Prudential Standard CPS 234 Information Security applies to the organization. Reference-depth scope is a decision-tree prompt; Full-depth plugins extend this with entity- and asset-aware logic.
Usage
/au-apra-cps-234:scope
What this produces
- **Applicability verdict**: in-scope, out-of-scope, or partially in-scope.
- **In-scope entity types**: APRA-regulated entity, RSE licensee, insurer,
authorised deposit-taking institution, related party, or third-party service provider supporting regulated operations.
- **In-scope assets**: information assets classified by sensitivity,
criticality, owner, hosting model, and dependency.
- **Jurisdiction reach**: APRA-regulated Australian operations and supporting
offshore, cloud, related-party, or outsourced services.
- **Next steps**: whether to proceed with `/au-apra-cps-234:assess` or
`/au-apra-cps-234:evidence-checklist`.
Framework-specific scope triggers
Ask the minimum questions needed to classify CPS 234 applicability:
- Is the organization an APRA-regulated entity or part of a regulated group?
- Does it manage information assets for an APRA-regulated entity?
- Which information assets are critical or sensitive?
- Which assets are managed by related parties, outsourced providers, cloud
services, or offshore teams?
- Who owns each information asset and who is accountable for control design,
control testing, and incident escalation?
- Are there materiality thresholds for information security incidents and
control weaknesses?
- Are control testing results, third-party assurance, and incident exercises
reported to board or senior management?
Return an applicability verdict, in-scope assets, accountable owners, and the follow-up command that should run next. Do not ask users to search CPS 234; translate their answers into practical scoping outcomes.
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.
Repo: GRCEngClub/claude-grc-engineering
Other commands on trust-center.
- /research
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing
Open command - /collect
Query AWS for compliance-relevant configuration across IAM, S3, CloudTrail, EBS, and emit findings conforming to the v1 contract.
Open command - /setup
Install the frdocx-to-froscal-ssp Python pipeline and verify its dependencies. Idempotent.
Open command - /status
Check the deployment status of the trust center.
Open command - /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.
Open command - /compliance-posture
Serve a localhost compliance posture dashboard from monitor-continuous JSON
Open command

