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

Basic Security Controls vs GDPR Romania

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

Basic Security Controls

GDPR RomaniaControllers and processors

At a Glance

They differ on 0 of 0 topics. Each verdict names what it rests on; read the wording before relying on it.

  • Basic Security Controls Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
  • GDPR Romania Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
Requirements per topic and verdict
Topic Basic Security ControlsGDPR Romania Verdict

What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

Status

Reviewed against the official texts.

Included

  • GDPR Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

National requirements

None recorded yet, so the Directive is shown as it is. The national law may go further.

Status

Reviewed against the official texts.

Key Numbers

Deadline

Basic Security Controls: Not in the acts covered

GDPR Romania: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Threshold

Basic Security Controls: Not in the acts covered

GDPR Romania: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

Goes to

Basic Security Controls: Not in the acts covered

GDPR Romania: Controller (Processors); Data subjects (Controllers)

Evidence to keep

Basic Security Controls: Not in the acts covered

GDPR Romania: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Incident reports go to

Basic Security Controls: Not in the acts covered

GDPR Romania: Competent supervisory authority (Controllers)

First notice of an incident

Basic Security Controls: Not in the acts covered

GDPR Romania: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

Intermediate report

Basic Security Controls: Not in the acts covered

GDPR Romania: In phases, without undue further delay (Controllers)

External assessment or certification

Basic Security Controls: Not in the acts covered

GDPR Romania: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Review of the risk framework

Basic Security Controls: Not in the acts covered

GDPR Romania: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Testing of critical systems

Basic Security Controls: Not in the acts covered

GDPR Romania: Regularly

Maximum fines

Basic Security Controls: Not in the acts covered

GDPR Romania: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022. 23 topics where all apply the Directive as it is are not shown.

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…