Home  /  Insights  /  ISO 27001 for fintechs and suppliers to banks
Insights

ISO 27001 for fintechs and suppliers to banks

If you sell to banks, insurers or super funds, or hold financial data yourself, security assurance is part of the product. Here’s what bank buyers ask for and why, how ISO 27001 sits with CPS 234, CPS 230, the Consumer Data Right, PCI DSS and AML/CTF, how to scope your ISMS, and the controls that get the hardest look.

Cyber Veda

Quick answer: ISO 27001 isn’t a legal requirement for Australian fintechs, but banks and other APRA-regulated buyers must assess their suppliers’ security under CPS 234 and manage material service providers under CPS 230, so an ISO 27001 certificate or SOC 2 report is usually a condition of doing business. ISO 27001 also counts as partial evidence for CDR accreditation, alongside a reduced-scope assurance report. It doesn’t replace PCI DSS where you handle card data, or your AML/CTF program.

Why banks ask their suppliers for ISO 27001

Banks, insurers and super funds are bound by two APRA standards that reach their suppliers. CPS 234 Information Security requires them to assess the information security capability of any third party that manages their information assets, evaluate the design of its controls and, in material cases, have internal audit assess the assurance it provides. CPS 230 Operational Risk Management, which commenced on 1 July 2025, requires them to identify material service providers, put specific terms in those agreements and monitor them. Providers of core technology services are treated as material unless the entity justifies otherwise.

Neither standard names ISO 27001. Both create a duty to check you, and a certificate from an accredited certification body is the fastest way to give a bank something it can rely on. We map CPS 234 to ISO 27001 clause by clause, and cover the CPS 230 contract terms, in CPS 234 vs ISO 27001. This guide covers everything else a fintech meets.

What bank vendor due diligence looks like

Expect a structured process rather than a single questionnaire:

  1. Tiering. The bank rates you by the data you will hold, the access you will have and how critical your service is. A payments or core banking provider gets far more scrutiny than a marketing tool.
  2. Evidence request. Your ISO 27001 certificate and its scope, your Statement of Applicability, a SOC 2 or ASAE 3150 report if you have one, a recent independent penetration test summary, your incident response and business continuity plans and their test results, and your internal audit outcome.
  3. Questionnaire. Often hundreds of questions, many already answered by your certificate. The rest cover data location, encryption, privileged access, your own subcontractors and how fast you will notify an incident. See how to answer security questionnaires faster.
  4. Contract. Security schedules, audit and access rights (including for APRA where you are material), notification timeframes, subcontracting approval, data return and exit assistance.
  5. Ongoing monitoring. Annual re-assessment, a fresh certificate or report each year, and notice of material changes.

Check the certificate scope before you send it. If it covers your Sydney office but not the platform the bank will use, the bank will notice.

ISO 27001 or SOC 2 for bank buyers

Australian banks accept both, and APRA’s guidance in CPG 234 asks entities to consider the scope, depth and independence of whatever assurance they rely on rather than naming one. The practical differences:

ISO 27001 certificateSOC 2 Type 2 report
What it showsYour management system conforms to the standard and is effectively implemented, with annual surveillance auditsA CPA firm’s opinion on whether your controls were designed and operated effectively over a period, usually 6 to 12 months
Who prefers itMost Australian and Asian banks, government-owned and international institutionsUS-owned institutions and internal audit teams that want tested operating effectiveness
ShareableCertificate shared freely and verifiable with the certification body; SoA shared under NDAReport shared under NDA
Australian alternativeAn ASAE 3150 controls assurance report, which some banks accept and the CDR regime recognises

The controls overlap heavily, so the second takes far less work than the first. See ISO 27001 vs SOC 2 and SOC 2 in Australia.

If you are regulated yourself

Many fintechs are not just suppliers. If you hold an Australian financial services licence or credit licence, your general obligations include adequate risk management systems, and the Federal Court found in ASIC’s case against RI Advice in 2022 that a licensee breached those obligations by failing to have adequate cyber security risk management. ISO 27001 doesn’t make you compliant with your licence, but it is strong evidence that your security risk management is systematic, documented and reviewed.

The Consumer Data Right

To receive CDR data as an accredited data recipient, you must meet the information security obligation in Schedule 2 of the CDR Rules: governance steps in Part 1 (security governance, defining the CDR data environment, a security capability, a controls assessment program and incident management) and minimum controls in Part 2. The ACCC’s supplementary accreditation guidelines on information security (version 6, April 2025) set out the evidence.

Unrestricted accreditation

You must provide independent evidence in one of four forms: a reasonable assurance report under ASAE 3150, ASAE 3402, ISAE 3000 or SOC 1/SOC 2; ISO 27001 certification plus a reduced-scope assurance report; Level 1 PCI DSS compliance plus a reduced-scope report; or top-tier ATO Digital Service Provider framework compliance plus a reduced-scope report. At application, the assurance report covers design and implementation at a point in time (Type I) and must be no more than three months old.

The guidelines are explicit that ISO 27001 alone doesn’t meet the obligation. If you use it, you submit:

  • your certificate and any recertification certificates;
  • an ISMS internal audit report no more than 12 months old covering all clauses and Annex A controls, by an auditor who is objective, impartial and not involved in the ISMS (an external internal auditor should hold an ISO 27001 Lead Auditor qualification);
  • your Statement of Applicability;
  • a reduced-scope assurance report covering the CDR data environment boundary and ten controls ISO 27001 doesn’t fully address: MFA for all access to CDR data, restricted administrative privileges, role-based access, unique IDs, strong password authentication, encryption at rest, encryption in transit, firewalls, server hardening and segregation of CDR data; and
  • an attestation that you can meet Schedule 2.

Ask the ACCC before relying on ISO 27001; the guidelines say to. Your certificate scope must cover the CDR data environment.

After accreditation

You provide a management attestation at the end of the first reporting period and every second year after (years 1, 3, 5), and an assurance report on operating effectiveness over at least 12 months (Type II) in years 2, 4 and 6. If you rely on ISO 27001, the ongoing evidence is your latest surveillance audit report plus a reduced-scope Type II report. Sponsored accreditation uses a self-assessment and attestation form instead of an independent report, and some fintechs avoid accreditation altogether by operating as a CDR representative of an accredited person, in which case the principal’s security requirements apply to you through the arrangement.

PCI DSS

If you store, process or transmit cardholder data, or your systems can affect its security, PCI DSS applies. The current version is 4.0.1, and its future-dated requirements became mandatory on 31 March 2025. Level 1 service providers need an annual Report on Compliance from a Qualified Security Assessor; others may be able to self-assess, depending on their level and their acquirer’s or card brands’ rules. ISO 27001 doesn’t replace any of this, but one ISMS can run both: PCI DSS becomes a contractual requirement in your clause 4.2 analysis and control 5.31 register, and its technical requirements sit inside your Annex A controls. The best effort-saver is scope reduction: tokenisation and hosted payment pages can take most of your environment out of PCI scope.

AML/CTF and the Privacy Act

Remitters, lenders, payment providers and virtual asset businesses are often AML/CTF reporting entities. The reformed AML/CTF obligations began applying to existing reporting entities on 31 March 2026, with newly regulated sectors following from 1 July 2026. The Act requires an AML/CTF program and record keeping, generally for seven years; it doesn’t set a security standard. But it makes you hold some of the most attractive data an attacker can steal: identity documents, verification results and transaction histories.

The Privacy Act applies to personal information you handle for AML/CTF purposes even if you are otherwise a small business. APP 11 requires reasonable steps, including technical and organisational measures, to protect it and to destroy or de-identify it when no longer needed, which has to be reconciled with AML/CTF retention periods. Notifiable data breaches go to the OAIC and affected individuals as soon as practicable. Your ISMS should record all of this under clause 4.2 and control 5.31 and reflect it in your retention and deletion rules. See Australia’s new cyber and privacy laws.

Scoping a fintech ISMS

Scope to what your financial customers and regulators rely on: the platform, its cloud environment, the integrations with banks, card schemes or data holders, and the people who build, run and support it. Then make sure the boundary lines up with your other obligations. Your CDR data environment, PCI cardholder data environment and the systems a bank will use should all sit inside the ISMS scope, or the certificate won’t do the work you need it to. The cloud scoping decisions are covered in ISO 27001 for SaaS companies.

The controls under most scrutiny

For what each control involves, see the Annex A controls explained.

AreaAnnex A controlsWhat banks and assessors check
Privileged access8.2 Privileged access rights, 5.18 Access rights, 8.5 Secure authenticationWho can reach production and customer data, time-limited admin rights, MFA everywhere, regular reviews
Cryptography8.24 Use of cryptographyEncryption at rest and in transit, key management and who can access keys
Logging and monitoring8.15 Logging, 8.16 Monitoring activitiesTamper-resistant logs, alerting on admin and data access, retention long enough for investigations
Change and development8.25 to 8.29 secure development and testing, 8.32 Change management, 8.33 Test informationPeer review, segregation between development and production, no real customer data in test
Vulnerabilities and testing8.8 Management of technical vulnerabilities, 8.9 Configuration managementPatch timeframes, hardening standards and independent penetration testing. See does ISO 27001 require penetration testing?
Segregation8.3 Information access restriction, 8.22 Segregation of networksHow one customer’s data is kept from another’s in a multi-tenant platform
Suppliers5.19 to 5.22 supplier controls, 5.23 Cloud servicesYour own subcontractors, their locations and the flow-down of bank contract terms
Incidents and resilience5.24 to 5.28 incident management, 5.29 and 5.30 continuity, 8.13 Information backupNotification commitments that let the bank meet APRA’s 72-hour deadline, recovery times tested against the bank’s tolerances

Common mistakes

  • A scope that misses the regulated environment. Certifying head office while the platform, CDR environment or cardholder environment sits outside scope.
  • Notification promises you can’t keep. Signing a bank contract that requires notice within hours when your incident procedure has no on-call process to deliver it.
  • Treating frameworks as separate projects. Running ISO 27001, PCI DSS and CDR evidence in parallel spreadsheets instead of one control set mapped to each.
  • Self-reviewed internal audits. An internal audit done by the person who built the ISMS fails ISO 27001’s impartiality requirement and the CDR guidelines’ independence test.
  • Retention conflicts. Deleting KYC records on a privacy request when AML/CTF requires you to keep them, or keeping everything forever “for AML”.

Mapping one ISMS to a bank’s assessment, CDR Schedule 2 and PCI DSS at the same time is the part we most often take on for fintech clients.

Effort and timing

A small or medium fintech can often be audit-ready in about eight weeks; see how long ISO 27001 takes. Effort grows with scope, the number of frameworks you must satisfy and how much evidence already exists. Our guide to what drives ISO 27001 cost explains the factors.

Next step

If you are building your ISMS yourself, ISO 27001 requires internal audits to be objective and impartial, so staff can do them only if they aren’t auditing their own work. That is why many small teams bring in an independent internal auditor. If you rely on ISO 27001 for CDR accreditation, the internal auditor must have had no part in designing, implementing or operating the ISMS. To talk through a bank’s requirements or a CDR application, book a free 30-minute consultation, or see how our ISO 27001 service works.

FAQ

Common questions

Do Australian banks require ISO 27001 from fintech suppliers?

Not by law. APRA’s CPS 234 requires banks to assess the information security capability of third parties that manage their information assets, and CPS 230 requires them to manage material service providers closely. In practice that means a security assessment of every significant supplier, and an ISO 27001 certificate or SOC 2 report is the evidence most banks expect to see.

Is ISO 27001 or SOC 2 better for selling to banks?

Australian banks accept both. ISO 27001 is the most widely recognised in Australia and Asia, and SOC 2 Type 2 is preferred by some US-owned institutions and by internal audit teams that want an opinion on operating effectiveness over a period. If you sell to one bank, ask which it accepts. See ISO 27001 vs SOC 2.

Can ISO 27001 be used for CDR accreditation?

Yes, as partial evidence. Under the ACCC’s information security guidelines (version 6, April 2025), an applicant for unrestricted accreditation can submit its ISO 27001 certificate, a recent internal audit report and its Statement of Applicability, together with a reduced-scope assurance report covering the CDR controls ISO 27001 doesn’t fully address, such as MFA, privileged access, encryption, server hardening and data segregation.

Does ISO 27001 replace PCI DSS?

No. If you store, process or transmit cardholder data, or can affect its security, PCI DSS applies through your card scheme and acquirer obligations, and ISO 27001 doesn’t satisfy it. The two overlap heavily, so one ISMS can run both, but they need separate assessments.

Does the AML/CTF Act require ISO 27001?

No. The AML/CTF Act requires reporting entities to have an AML/CTF program and to keep customer identification and transaction records, generally for seven years. It doesn’t name a security standard. The Privacy Act applies to the personal information you collect for AML/CTF purposes, even if you are a small business, and ISO 27001 is a strong way to protect it.

Talk to someone who has taken companies like yours to audit.

Book a free 30-minute consultation. Tell us what is driving the need, and leave with a realistic timeline and the first three things to do.