What are we working on?
Ask a question, create an output, or build an app that works with your tools and data.
Get Started
Build a transaction fraud monitoring dashboard
Monitor fraud attempts, AML alerts, and security posture across banking channels
App
Monitor fraud attempts, AML alerts, and security posture across banking channels
Draft an APRA CPS 234 compliance runbook
Generate a runbook grounded in your security standards and APRA guidance
Document
Generate a runbook grounded in your security standards and APRA guidance
Build a Q3 platform engineering review deck
Pull data from Jira and Confluence into slides
Slide Deck
Pull data from Jira and Confluence into slides
Connect to our transaction monitoring system and build a real-time fraud dashboard showing suspicious transaction volumes, blocked payments, AML alerts, and risk scores across banking channels.
AI
I'll need access to your transaction monitoring and fraud detection systems. Let me request that through a Gatekeeper.
🔒 Gatekeeper: Transaction Monitoring Engine
Requesting read-only access to fraud telemetry, transaction risk scores, AML alert data, and channel security metrics. The Gatekeeper holds the credential and logs every query.
Requesting read-only access to fraud telemetry, transaction risk scores, AML alert data, and channel security metrics. The Gatekeeper holds the credential and logs every query.
Approved.
AI
Access granted. Pulling transaction monitoring data now.
Executed code
const monitoring = await env.TXN_MONITOR.getFraudTelemetry({
channels: "all-banking",
include: ["fraud_rate", "blocks", "aml_alerts", "risk_scores"]
});
const activeAlerts = monitoring.incidents.filter(
i => i.severity === "critical" || i.severity === "high"
);
app.render(FraudDashboard, { monitoring, activeAlerts });
AI
Transaction Fraud Monitoring Dashboard is live. Connected via Gatekeeper -- read-only, every query logged.
I see 3 active alerts requiring attention, including an account takeover campaign targeting NetBank login. Want me to set up PagerDuty escalation if the fraud block rate drops below 99%?
I see 3 active alerts requiring attention, including an account takeover campaign targeting NetBank login. Want me to set up PagerDuty escalation if the fraud block rate drops below 99%?
+
Draft an updated APRA CPS 234 Information Security compliance runbook. Base it on our current security standards and the latest APRA prudential guidance.
AI
I'll pull from your company's context library to ground this in CBA's standards.
📚 Context Library: Security & Compliance
Loading CBA's security standards (v5.2), APRA CPS 234 requirements, compliance framework, and incident management procedures. These are curated by your security team and read-only to the agent.
Loading CBA's security standards (v5.2), APRA CPS 234 requirements, compliance framework, and incident management procedures. These are curated by your security team and read-only to the agent.
AI
Context loaded. I've identified 5 key compliance areas to address in the runbook:
1. Information asset classification and criticality assessment
2. Security control testing and assurance
3. Vulnerability management and patch cadence
4. Incident notification to APRA (72-hour requirement)
5. Board reporting and governance obligations
I'll structure the runbook around these APRA requirements.
1. Information asset classification and criticality assessment
2. Security control testing and assurance
3. Vulnerability management and patch cadence
4. Incident notification to APRA (72-hour requirement)
5. Board reporting and governance obligations
I'll structure the runbook around these APRA requirements.
AI
APRA CPS 234 Compliance Runbook v3.0 draft is ready. Structured per APRA's prudential framework with control evidence mapping and audit trail requirements.
You can edit directly, export to Google Docs, or share for review. The document stays connected to the context library -- if APRA guidance changes, I can flag sections that need updating.
You can edit directly, export to Google Docs, or share for review. The document stays connected to the context library -- if APRA guidance changes, I can flag sections that need updating.
+
Build a Q3 platform engineering review deck summarising our infrastructure changes, cloud migration status, and upcoming initiatives. Pull data from Jira and Confluence.
AI
I'll need access to your project tracking and wiki.
🔒 Gatekeeper: Jira (read-only)
Requesting access to the PLATFORM and INFRA projects. Read epics, status, and completion data only.
Requesting access to the PLATFORM and INFRA projects. Read epics, status, and completion data only.
🔒 Gatekeeper: Confluence (read-only)
Requesting access to the Architecture Decisions space. Read pages only.
Requesting access to the Architecture Decisions space. Read pages only.
Both approved.
AI
Executed code
const epics = await env.JIRA.getEpics({
projects: ["PLATFORM", "INFRA"],
quarter: "Q3-2026"
});
const adrs = await env.CONFLUENCE.getPages({
space: "architecture-decisions",
since: "2026-07-01"
});
deck.generate(QuarterlyReview, { epics, adrs });
AI
Q3 Platform Engineering Review deck is ready -- 4 slides from live Jira and Confluence data.
You can regenerate anytime to pick up changes, or edit individual slides. Export to Google Slides or PDF when ready to present.
You can regenerate anytime to pick up changes, or edit individual slides. Export to Google Slides or PDF when ready to present.
+
Gadget
Code
Connections
Transaction Fraud Monitoring Dashboard
99.7%
Fraud Block Rate
3
Active Alerts
1.8M
Blocked Transactions Today
94
Risk Posture Score
Active Alerts
🔴 Account Takeover -- NetBank Login -- 9.2K credential stuffing attempts/hr from rotating proxies. Bot management rules engaged, 99.6% blocked.
🔴 Unusual Cross-Border Pattern -- Anomalous high-value transfer pattern across 5 accounts flagged by AML model. Under investigation by Financial Crime team.
⚠️ Card-Not-Present Spike -- 34% increase in CNP fraud attempts on CommBiz merchant gateway. Enhanced 3DS checks activated.
Risk Score by Channel
NetBank
82%
Elevated
CommBiz
91%
Secure
Card Payments
88%
Secure
CommBank App
96%
Secure
Branch Systems
97%
Secure
ATM Network
93%
Secure
Open Banking APIs
71%
At Risk
Page
Source
Connections
APRA CPS 234 Compliance Runbook v3.0
CBA -- APRA CPS 234 Information Security Compliance Runbook
1. Purpose
This runbook defines CBA's end-to-end procedures for maintaining compliance with APRA Prudential Standard CPS 234 (Information Security). It applies to all information assets, including those managed by related parties and third-party service providers, and is aligned with CBA's Information Security Management System (ISMS) and the APRA prudential framework.
2. Scope
- All critical and material information assets across retail, institutional, and markets divisions
- Third-party and cloud service provider arrangements (AWS, Azure)
- Information security controls testing and assurance program
- APRA incident notification procedures (72-hour requirement) [NEW]
- Board and senior management governance obligations [NEW]
3. Compliance Phases
| Phase | Description | Frequency | Gate |
|---|---|---|---|
| 1. Asset Classification | Classify information assets by criticality and sensitivity, map to business processes | Annual + trigger | 100% coverage |
| 2. Control Assessment | Test information security controls commensurate with asset criticality | Quarterly | All critical controls tested |
| 3. Vulnerability Mgmt | Identify, prioritise, and remediate vulnerabilities within SLA | Continuous | Critical: 48hr, High: 7 days |
| 4. Incident Notification | Notify APRA within 72 hours of material information security incidents | Event-driven | APRA notified < 72hr |
| 5. Board Reporting | Provide Board with information security compliance status and material risks | Quarterly | Board paper submitted |
APRA Notification Requirement: CBA must notify APRA as soon as possible and no later than 72 hours after becoming aware of a material information security incident. The CISO or delegate must authorise all APRA notifications. Refer to incident-management.md for escalation paths.
4. Remediation Tracking
| Finding Severity | Remediation SLA | Escalation |
|---|---|---|
| Critical vulnerability | < 48 hours | CISO + CRO immediately |
| High-risk control gap | < 7 days | CISO at next business day |
| APRA audit finding | Per APRA timeline | Board Risk Committee |
| Third-party control deficiency | < 30 days | Third-Party Risk team |
Slides
Source
Connections
Q3 Platform Engineering Review
Integrations
Connect external services to CBA OS. Gatekeepers govern access, scope permissions, and log every action.
Gatekeepers
Google Workspace
Gmail, Docs, Sheets, Slides, Calendar, Drive
Slack
Send messages, read channels, manage workflows
Jira
Projects, epics, issues, sprints, and boards
Confluence
Read and write wiki pages, search spaces
GitHub Enterprise
Access repositories, create PRs, manage issues and actions
PagerDuty
On-call schedules, incident alerts, and escalation policies
Splunk
Security events, SIEM alerts, log analytics, and threat correlation
ServiceNow
IT tickets, change requests, CMDB, and incident management
Snowflake
Data warehouse, analytics, cross-department reporting
Grafana
Dashboards, observability, metrics, and alerting
Workday
Employee data, org charts, payroll, time off, benefits
Datadog
APM, infrastructure monitoring, log management, and tracing
MCP Servers
Remote MCP servers available to all workspaces.
Transaction Monitoring Engine
https://txn-monitor.mcp.cba.internal/mcp
Auto
Core Banking API
https://core-banking.mcp.cba.internal/mcp
Needs auth
Risk & Fraud Engine
https://risk.mcp.cba.internal/mcp
Auto
Network Topology Service
https://network.mcp.cba.internal/mcp
Auto
Cloudflare API
https://mcp.cloudflare.com/mcp
Auto
Context
Curated reference documents that ground your agent in CBA's knowledge. Published centrally, read-only to all agents and workspaces.
company-strategy-fy2027.md
CBA's strategic priorities, digital banking vision, annual objectives, and key results by division
security-standards.md
Information security policies, APRA CPS 234 controls, cryptographic standards, and access management
architecture-principles.md
Platform architecture standards, microservices guidelines, decision criteria, and technology radar
api-design-guidelines.md
REST/GraphQL API conventions, Open Banking CDR data standards, versioning, and rate limiting
compliance-framework.md
APRA CPS 234, APRA CPS 230, Privacy Act 1988, AML/CTF Act, CDR regulatory requirements and control mappings
infrastructure-inventory.md
System catalogue with ownership, SLAs, dependency mappings, and change advisory contacts
developer-standards.md
Coding standards, CI/CD pipeline requirements, testing coverage thresholds, and release procedures
risk-management-playbook.md
Fraud detection models, risk scoring methodology, AML/CTF procedures, and transaction monitoring thresholds
network-architecture.md
Network topology, data centre inventory (SYD, MEL), DNS architecture, and peering agreements
incident-management.md
Incident response procedures, APRA notification workflows, war room protocols, and post-mortem templates
Skills
| Name | Description | Group | Source |
|---|---|---|---|
| meeting-prep | Scan calendar, gather context from connected systems, and generate briefing docs | General | CBA |
| weekly-report | Compile team activity summaries from Jira, Slack, email, and calendar data | General | CBA |
| threat-assessment | Analyse threat intelligence feeds, correlate attack patterns, and generate risk briefings | Security | CBA |
| fraud-model-tuning | Review fraud model performance, suggest threshold adjustments, and generate tuning reports | Security | CBA |
| apra-compliance | Gather APRA CPS 234/CPS 230 compliance evidence, map controls, and generate audit packages | Security | CBA |
| incident-response | Draft or update incident response policies grounded in CBA security standards and APRA guidance | Security | CBA |
| vulnerability-triage | Prioritise CVEs against CBA's asset inventory, assign owners, and track remediation SLAs | Security | CBA |
| aml-investigation | Support AML/CTF investigations with transaction pattern analysis and suspicious matter reporting | Risk | CBA |
| credit-risk-review | Generate credit risk summaries, portfolio exposure analysis, and provision adequacy reports | Risk | CBA |
| architecture-review | Build quarterly architecture review decks from Jira and Confluence data | Engineering | CBA |
| api-catalogue | Discover, document, and visualise internal API endpoints with ownership and health | Engineering | CBA |
| service-health | Generate service reliability reports from monitoring data, SLO tracking, and incident history | Engineering | CBA |
| deployment-runbook | Create step-by-step deployment guides with pre-checks, rollback procedures, and verification | Engineering | CBA |
| cloud-migration | Plan and track AWS/Azure migration workloads, dependency mapping, and cutover checklists | Infrastructure | CBA |
| capacity-planning | Forecast compute, storage, and network capacity needs based on traffic trends and growth | Infrastructure | CBA |
| cost-optimisation | Cloud and infrastructure spend analysis, trend visualisation, and optimisation recommendations | Infrastructure | CBA |
| change-impact | Analyse change impact across systems, map dependencies, and identify affected teams | Engineering | CBA |