<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Guideline on  security measures under the EECC</title>
  </titleInfo>
  <name type="personal">
    <namePart>Milenkovic, Goran</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Dekker , Marnix</namePart>
  </name>
  <name type="corporate">
    <namePart>European Union Agency for Cybersecurity</namePart>
  </name>
  <typeOfResource>text</typeOfResource>
  <genre authority="marc">technical report</genre>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">gr</placeTerm>
    </place>
    <place>
      <placeTerm type="text">Attiki, Greece</placeTerm>
    </place>
    <publisher>: ENISA</publisher>
    <dateIssued>December 2020</dateIssued>
    <dateIssued encoding="marc">2020</dateIssued>
    <edition>3rd ed</edition>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
    <internetMediaType>pdf</internetMediaType>
    <extent>60 p.  : gráf. ; 1 documento PDF</extent>
  </physicalDescription>
  <abstract>This document, the Technical Guideline for Security Measures, provides guidance to competent authorities about the technical details of implementing Articles 40 and 41 of the EECC: how to ensure that providers assess risks and take appropriate security measures. The guideline lists 29 high-level security objectives, which are grouped in 8 security domains. For each security objective we list specific detailed security measures which could be taken by providers to reach the security objective. These security measures are grouped in 3 levels of increasing sophistication. We also give examples of evidence, which could be taken into account by an auditor, for example, when assessing if these security measures are actually in place.</abstract>
  <targetAudience authority="marctarget">specialized</targetAudience>
  <note type="statement of responsibility">/ Authors, Goran Milenkovic and Dr. Marnix Dekker, European Union Agency for Cybersecurity</note>
  <note>Reproduction is authorised provided the source is acknowledged.</note>
  <subject authority="lcsh">
    <topic>Ciberseguridad y confianza</topic>
  </subject>
  <subject>
    <topic>cybersecurity </topic>
    <topic>security measures</topic>
  </subject>
  <subject>
    <topic>EECC</topic>
  </subject>
  <subject>
    <topic>European Electronic Communications Code</topic>
  </subject>
  <identifier type="isbn">978-92-9204-457-2</identifier>
  <identifier type="uri">https://www.enisa.europa.eu/publications/guideline-on-security-measures-under-the-eecc</identifier>
  <location>
    <url displayLabel="Acceso al documento">https://www.enisa.europa.eu/publications/guideline-on-security-measures-under-the-eecc</url>
  </location>
  <accessCondition type="useAndReproduction">Reproduction is authorised provided the source is acknowledged.</accessCondition>
  <recordInfo>
    <recordContentSource authority="marcorg">ES-MaONT</recordContentSource>
    <recordCreationDate encoding="marc">201211</recordCreationDate>
    <recordChangeDate encoding="iso8601">20250327102720.0</recordChangeDate>
    <recordIdentifier source="ES-MaONT">00006275</recordIdentifier>
  </recordInfo>
</mods>
