Incident to report to a regulator?Incident to report? Intake Line

Standard and framework · Slovakia · TIBER-SK Implementation document

TIBER-SK: Threat Intelligence-Based Ethical Red Teaming Framework

TIBER-SK sets out how threat-led penetration tests run in Slovakia.

Last updated 6 November 2026

What Is TIBER-SK?

To set out how threat-led penetration tests of financial entities run in Slovakia.

TIBER-SK is the Slovak implementation of TIBER-EU, published by the National Bank of Slovakia in June 2025. It is fully compatible with TIBER-EU and with the DORADigital Operational Resilience Act requirements for threat-led penetration testingA framework that mimics the tactics, techniques and procedures of real attackers to test an organisation's live critical functions. DORA requires certain financial entities to carry out TLPT regularly..

It is aimed at financial entities that play a systemic or important role in Slovakia. Entities outside mandatory testing can ask for a voluntary test, subject to cyber maturity and team availability.

Full title
Threat Intelligence-Based Ethical Red Teaming (TIBER-SK)
Original title
TIBER-SK Implementation document
Official reference
TIBER-SK Implementation document, June 2025
Type
Framework
Issued by
National Bank of Slovakia
Status
In force
Countries
Slovakia

Get regulatory updates

One email a week when something changes in the countries you choose, TIBER-SK included.

Countries
Slovakia

Pick one or more

One email a week, only when something changed. Each email has an unsubscribe link. Privacy notice

What TIBER-SK Requires

TIBER-SK

Control team

Set up a control team led by a Control Team Lead, and keep knowledge of the test within it apart from board-level approvals.

TIBER-SK

Third-party participation

Take all necessary measures to ensure ICTInformation and Communication Technology third-party providers that support a critical or important functionA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. take part.

TIBER-SK

Threat intelligence

Use an external threat intelligenceInformation about cyber threats that has been collected, combined and analysed to help people make security decisions. It adds context to facts about attackers, their methods or signs of an attack, helping an organisation judge what matters to its systems. It can guide monitoring, incident response, information sharing and realistic attack simulations. provider, and select at least three scenarios for the targeted report.

TIBER-SK

Active testing

Run active red teamA group authorised to imitate an attacker in order to test an organisation's security. The team uses realistic attack methods to show what an adversary could achieve and how well the organisation detects and responds. The results help defenders improve their controls and response. In financial-sector testing, the team's activities must follow the agreed test scope and safeguards. testing for at least 12 weeks on live production systems, with stakeholder meetings at least weekly.

Show All 5 Requirements

TIBER-SK

Closure

Produce the final test summary report and a remediation plan, and repeat testing every three years unless the interval is changed.

How We Help With TIBER-SK

Start with an assessment, or have us run the work.

Preparing for TIBER-SK?

Thirty minutes with a GRC+ consultant: we look at your scope, the requirements that apply and where to start.

Loading the form…