Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is an SPK Information Systems Audit?

An SPK information systems audit is the independent examination that Turkey’s capital markets regulator requires of brokerages, fund managers, and market infrastructure, based on a recognised governance framework.

Illustration for the cybersecurity term SPK Information Systems Audit
Home / Blog / Cybersecurity Terms / What Is an SPK Information Systems Audit?
17 November 2026

What Is an SPK Information Systems Audit?

What Is an SPK Information Systems Audit?

Turkey’s Capital Markets Board, known by its Turkish initials SPK, requires the institutions it supervises to have their information systems examined by an independent audit firm. The obligation rests on two communiqués issued at the start of 2018: one setting out how information systems must be managed, and one governing the independent audit of those systems. Together they make technology governance a supervised matter for the capital markets sector in the same way that financial reporting already was.

UK readers meet this when a group includes a Turkish brokerage or portfolio management company, or when a London entity provides technology services to one. The audit scope reaches outsourced providers, so a UK supplier may find itself producing evidence for an audit it is not a party to.

Who Is in Scope

The audit is carried out by firms authorised by the Board for this work, not by the institution’s internal audit function, and the report goes to the Board. The audit cycle is periodic rather than continuous, with the frequency depending on the type of institution.

What the Audit Examines

The management communiqué expects a structured approach built on a recognised framework, with COBIT the reference point in practice, and the audit tests whether that structure exists and works. The recurring areas are:

  1. Governance. Board-level responsibility for information systems, a strategy, defined roles, and a risk management process that is actually used.
  2. Information security. Access management, segregation of duties, cryptography, network protection, vulnerability management, and incident handling.
  3. Change and configuration management. Authorisation, testing, and separation between development, test, and production environments, which is where findings cluster.
  4. Business continuity and disaster recovery. Documented plans, recovery objectives, and evidence of testing rather than assertion.
  5. Data integrity. Completeness and accuracy of transaction and client records, with reconciliation controls.
  6. Outsourcing. Due diligence, contracts, audit rights, and oversight of service providers, including cloud providers.
  7. Application controls in the trading, order management, and client reporting systems that the business depends on.

How It Compares with the UK

The United Kingdom has no direct equivalent. The FCA does not mandate a recurring independent information systems audit for investment firms as a class. What it does instead is set outcomes and hold named individuals responsible for them.

Turkey, SPKUK, FCA and PRA
MechanismPeriodic independent audit against a governance frameworkOperational resilience rules, outsourcing expectations, and supervision
Who assessesAn audit firm authorised by the regulatorThe firm itself, with the regulator reviewing evidence
AccountabilityInstitutional, through the audit reportIndividual, through the Senior Managers and Certification Regime
Technical testingPart of the audit scopeThreat-led testing under CBEST for the largest firms

The practical difference is cultural as much as legal. A Turkish capital markets institution plans its year around an audit and produces evidence for an external examiner on a defined timetable. A UK firm maintains continuous evidence that it can remain within its impact tolerances and expects the regulator to ask about it at any time. Neither approach is obviously superior, and a group operating in both markets usually finds that the Turkish audit produces a more complete evidence pack while the UK regime produces faster remediation.

Preparing for One

Three things separate a smooth audit from a painful one. First, evidence must be contemporaneous: dated tickets, approval records, test results, and logs, not documents written the week before the auditor arrives. Second, scope must be agreed early, including which outsourced components are in and what access the auditor needs to a provider’s environment. Third, the previous year’s findings must be closed with evidence, because an unresolved finding repeated across cycles attracts far more attention than a new one.

Technical validation is worth running ahead of the audit rather than during it. Vulnerability management, access review, and segregation of environments are the areas where documented process and actual configuration most often disagree, and finding that out yourself is considerably cheaper.

Our regulation and compliance services provide the gap analysis and technical testing behind an information systems audit, including the evidence that outsourced providers are controlled as the contracts claim.

FAQ – Frequently Asked Questions

Is an SPK Audit the Same as an ISO 27001 Certification?

No. ISO 27001 certifies a management system against an international standard, chosen voluntarily and audited by a certification body. The SPK audit is a regulatory obligation examining compliance with the Board’s own communiqués, carried out by a firm the Board has authorised, with the report going to the regulator. An ISO 27001 certificate reduces the work substantially but does not replace the audit.

Does the Audit Cover Cloud Providers?

It covers the institution’s management of them. Outsourcing arrangements, due diligence, contractual audit rights, and ongoing oversight are explicitly within scope, and auditors increasingly ask for evidence drawn from the provider, such as assurance reports and configuration records. Agree early what the provider will supply, because retrofitting audit rights into a signed cloud contract is rarely possible.

What Findings Come Up Most Often?

Segregation between development, test, and production environments; privileged access that is granted broadly and reviewed rarely; change records that lack evidence of testing or approval; business continuity plans that have never been exercised; and user access reviews that are signed off without anyone examining the underlying entitlements. None of them are exotic, and all of them are visible in advance.

Do UK Firms Face Anything Similar?

Not in the same form. UK investment firms work to the FCA and PRA operational resilience rules, outsourcing expectations, and individual accountability under the Senior Managers and Certification Regime, with threat-led CBEST testing reserved for the largest institutions. The obligations overlap in substance, but there is no recurring mandatory independent information systems audit for the sector as a whole.

Related Terms

You May Be Interested In These

What Is Typosquatting?

Cybersecurity Terms

17 November 2026

What Is Typosquatting?

Read More
What Is Cross-Site Scripting (XSS)?

Cybersecurity Terms

17 November 2026

What Is Cross-Site Scripting (XSS)?

Read More
What Are Reputation Feeds?

Cybersecurity Terms

17 November 2026

What Are Reputation Feeds?

Read More