The first TIBER-EU phase, lasting up to six months from the authority's written notification: notification and initiation, setting up the control team and risk management, scoping critical or important functions and flags, and procuring the threat intelligence provider and red team testers.
How a TIBER-EU test starts: the authority's written notification, assignment of a test manager, the initiation documents and meeting due within three months, the test code name, and set-up and validation of the control team.
Choosing the critical or important functions to test, identifying the systems behind each and setting flags, and documenting it in the scope specification document due within six months, approved by the management body and validated by the authority.
Selecting and contracting the external threat intelligence provider and red team testers: minimum team, experience and reference requirements, evidence the control team gives the test manager, contract clauses, internal testers, and the deadline for completing procurement.
How the tested entity keeps a live-production test safe: the control team's documented risk assessment before and during testing, backup checks, confidentiality and escalation procedures, code names, the power to halt the test, and the test manager's oversight.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.