> GDPR Lithuania vs Information Security Management Framework side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# GDPR Lithuania vs Information Security Management Framework

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

[GDPR Lithuania](https://grc.plus/regulation/general-data-protection-regulation-gdpr/lithuania/)Controllers and processors

[Information Security Management Framework](https://grc.plus/regulation/information-security-management-framework-government/)

## At a Glance

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

- **GDPR Lithuania** Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- **Information Security Management Framework** Asks more on 0 topics Alone on 0 topics More detailed on 0 topics

| Topic | GDPR Lithuania | Information Security Management Framework | 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

- [GDPR](https://grc.plus/regulation/general-data-protection-regulation-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.

Included

- [Information Security Management Framework](https://grc.plus/regulation/information-security-management-framework-government/) GC_F5_Information_Security, version 1.0 3 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

GDPR Lithuania: At the time the data are obtained (Controllers); 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 (Controllers); 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 (Controllers); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (Controllers); 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 (Controllers)

Information Security Management Framework: Not in the acts covered

### Threshold

GDPR Lithuania: 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)

Information Security Management Framework: Not in the acts covered

### Goes to

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

Information Security Management Framework: Not in the acts covered

### Evidence to keep

GDPR Lithuania: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (Controllers)

Information Security Management Framework: Not in the acts covered

### Incident reports go to

GDPR Lithuania: Competent supervisory authority (Controllers)

Information Security Management Framework: Not in the acts covered

### First notice of an incident

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

Information Security Management Framework: Not in the acts covered

### Intermediate report

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

Information Security Management Framework: Not in the acts covered

### External assessment or certification

GDPR Lithuania: Approved code of conduct or certification may help show compliance (Controllers)

Information Security Management Framework: Not in the acts covered

### Review of the risk framework

GDPR Lithuania: Where necessary (Controllers)

Information Security Management Framework: Not in the acts covered

### Testing of critical systems

GDPR Lithuania: Regularly

Information Security Management Framework: Not in the acts covered

### Maximum fines

GDPR Lithuania: 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

Information Security Management Framework: Not in the acts covered

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.

## More Comparisons

- [Compare GDPR Lithuania](https://grc.plus/compare/gdpr-lithuania/)
- [Compare Information Security Management Framework](https://grc.plus/compare/information-security-management-framework/)

Source: https://grc.plus/compare/gdpr-lithuania-vs-information-security-management-framework/
