Category

Evaluación de conformidad

Algunas claves del Reglamento nº 910/2014 (EIDAS)

By | Evaluación de conformidad, Sin categoría | No Comments

I.- Utilización de sistemas de identificación y firma de forma transfronteriza

La transposición de la Directiva 1999/93 se realizó de forma irregular y nunca ha parecido que estuviera suficientemente claro que los certificados de firma electrónica e identificación expedidos por los Prestadores de Servicios de Certificación de un Estado miembro tuvieran que ser admitidos por el resto de los estados, en particular en sus servicios de administración electrónica.

Desde el 1 de julio de 2016 por la aplicación directa del Reglamento UE 910/2014 este concepto queda aclarado definitivamente. Veremos cómo se va asumiendo en las implementaciones.

II.- Los PSC (Prestadores de Servicios de Certificación) se denominarán PSEC (Prestadores de Servicios Electrónicos de Confianza)

Ahora se denominan Prestadores de Servicios de Confianza. Y pueden expedir certificados cualificados (equivalentes a los certificados reconocidos de la Ley 59/2003) o certificados no cualificados.

Un tipo concreto de servicio de confianza es la expedición de certificados de persona física, (lo que es compatible con el servicio previsto en la Ley 59/2003) y entre ellos los certificados cualificados (en la citada ley se les llamaba “reconocidos”).

Debe presentarse al organismo de supervisión (en España, la Secretaría de Estado de Telecomunicaciones y Sociedad de la Información) una notificación de su intención junto con un informe de evaluación de la conformidad expedido por un Organismo de Evaluación de la Conformidad (en España, la Entidad Nacional de Acreditación). Si se le concede la posibilidad de expedir certificados cualificados, se le incluirá en una lista de confianza (que cada Estado Miembro publicará con información de todos los Prestadores Cualificados de Servicios de Confianza) y podrá usar la etiqueta de confianza “UE”, para indicar los servicios que presta.

Es de destacar que aumentan los mecanismos de control sobre todos los prestadores de servicios (tanto si expiden certificados cualificados como si no), los cuales serán auditados cada 24 meses para confirmar que cumplen con lo dispuesto en el Reglamento.

III.- La responsabilidad de los prestadores de servicios

Siguen siendo responsables de los perjuicios causados de forma deliberada o por negligencia a cualquier persona en razn del incumplimiento de las obligaciones establecidas en el Reglamento. Sin embargo, se eliminan las limitaciones de la responsabilidad del artculo 23 de la Ley 59/2003, siendo la carga de la prueba (i) de la persona que alegue el daño, cuando el prestador expide certificados no cualificados, o (ii) del prestador de servicios que expide certificados cualificados, debiendo este probar que los perjuicios se produjeron sin intención ni negligencia alguna por su parte.

IV.- Los certificados de persona jurdica

El Reglamento no prevé la emisión de certificados de firma electrónica a favor de personas jurdicas o entidades sin personalidad jurdica. A este tipo de entidades reserva únicamente los sellos electrónicos, que permiten acreditar la autenticidad del origen y la integridad del documento sellado.

V.- Los nuevos servicios regulados

Aparte de la firma electrónica (definida, como en la Ley 59/2003, en 3 tipos, firma electrónica, avanzada y cualificada), el Reglamento también regula el sello electrónico (del que también se diferencian 3 tipos), el sello de tiempo electrónico, el servicio de entrega electrónica certificada, el documento electrónico y la autenticación del sitio web. El considerando 55 del Reglamento abre además la posibilidad de generar firmas electrónicas cualificadas como la firma móvil o la firma en nube, lo cual puede dinamizar enormemente el mercado de la firma electrónica.

DECISIÓN DE EJECUCIÓN (UE) 2016/650 DE LA COMISIÓN de 25 de abril de 2016 – evaluación de la seguridad de los dispositivos cualificados de creación de firmas y sellos electrónicos

By | #eIdAS, Evaluación de conformidad, Sin categoría | No Comments

DECISIÓN DE EJECUCIÓN (UE) 2016/650 DE LA COMISIÓN de 25 de abril de 2016 por la que se fijan las normas para la evaluación de la seguridad de los dispositivos cualificados de creación de firmas y sellos con arreglo al artículo 30, apartado 3, y al artículo 39, apartado 2, del Reglamento (UE) n.o 910/2014 del Parlamento Europeo y del Consejo, relativo a la identificación electrónica y los servicios de confianza para las transacciones electrónicas en el mercado interior

(Texto pertinente a efectos del EEE)

LA COMISIÓN EUROPEA,

Visto el Tratado de Funcionamiento de la Unión Europea,

Visto el Reglamento (UE) n.o 910/2014 del Parlamento Europeo y del Consejo, de 23 de julio de 2014, relativo a la identificación electrónica y los servicios de confianza para las transacciones electrónicas en el mercado interior y por el que se deroga la Directiva 1999/93/CE (1), y en particular su artículo 30, apartado 3, y su artículo 39, apartado 2,

Considerando lo siguiente:

(1)

El anexo II del Reglamento (UE) n.o 910/2014 establece los requisitos aplicables a los dispositivos cualificados de creación de firmas electrónicas y a los dispositivos cualificados de creación de sellos electrónicos.

(2)

La labor de elaborar las especificaciones técnicas necesarias para la producción y comercialización de productos que se adecúen al estado actual de la técnica la llevan a cabo las organizaciones competentes en el ámbito de la normalización.

(3)

La ISO/CEI (Organización Internacional de Normalización/Comisión Electrotécnica Internacional) establece los conceptos y principios generales de seguridad de la tecnología de la información y especifica el modelo general de evaluación que debe utilizarse como base para evaluar las propiedades de seguridad de los productos informáticos.

(4)

En el marco del mandato de normalización M/460 otorgado por la Comisión, el Comité Europeo de Normalización (CEN) ha elaborado normas aplicables a los dispositivos cualificados de creación de firmas y sellos electrónicos, cuando los datos de creación de firma electrónica o los datos de creación de sello electrónico se conservan íntegramente, aunque no necesariamente de forma exclusiva, en un entorno gestionado por el usuario. Esas normas se consideran adecuadas para evaluar la conformidad de tales productos con los requisitos pertinentes establecidos en el anexo II del Reglamento (UE) n.o 910/2014.

(5)

El anexo II del Reglamento (UE) n.o 910/2014 establece que solo un prestador cualificado de servicios de confianza puede gestionar datos de creación de firma electrónica en nombre del firmante. Los requisitos de seguridad y sus respectivas especificaciones de certificación difieren cuando el firmante posee físicamente un producto y cuando un prestador cualificado de servicios de confianza actúa en nombre del firmante. Para abordar ambas situaciones y favorecer con el tiempo el desarrollo de productos y criterios de evaluación adaptados a necesidades concretas, el anexo de la presente Decisión debe enumerar normas que abarquen ambas situaciones.

(6)

En el momento de la adopción de la presente Decisión de la Comisión, varios prestadores de servicios de confianza ya ofrecen soluciones para gestionar los datos de creación de firma electrónica en nombre de sus clientes. Las certificaciones de productos se limitan actualmente a los módulos de seguridad de los equipos informáticos certificados con arreglo a diferentes normas, pero todavía no están certificados específicamente con arreglo a los requisitos aplicables a los dispositivos cualificados de creación de sellos y firmas. No obstante, no existen aún normas publicadas, como la norma EN 419 211 (aplicable a la firma electrónica creada en un entorno íntegramente gestionado, aunque no necesariamente de forma exclusiva, por el usuario), para un mercado igualmente importante de productos a distancia certificados. Dado que se están elaborando actualmente las normas que podrían ser adecuadas a tal fin, la Comisión completará la presente Decisión cuando esas normas estén disponibles y se consideren conformes a los requisitos establecidos en el anexo II del Reglamento (UE) n.o 910/2014. Hasta el momento en que se establezca la lista de tales normas, puede utilizarse un proceso alternativo para evaluar la conformidad de esos productos en las condiciones previstas en el artículo 30, apartado 3, letra b), del Reglamento (UE) n.o 910/2014.

(7)

En el anexo figura la norma EN 419 211, que consta de diferentes partes (1 a 6) que abarcan distintas situaciones. Las partes 5 y 6 de dicha norma presentan extensiones relacionadas con el entorno de los dispositivos cualificados de creación de firma, como la comunicación con aplicaciones de creación de firma de confianza. Los fabricantes de productos son libres de aplicar esas extensiones. De conformidad con el considerando 56 del Reglamento (UE) n.o 910/2014, el objeto de la certificación en virtud de los artículos 30 y 39 de dicho Reglamento se limita a proteger los datos de creación de firmas, mientras que las aplicaciones de creación de firmas quedan excluidas del alcance de la certificación.

(8)

A fin de garantizar que las firmas o sellos electrónicos generados por un dispositivo cualificado de creación de firma o sello estén protegidos con seguridad contra la falsificación, como exige el anexo II del Reglamento (UE) n.o 910/2014, una condición indispensable para la seguridad del producto certificado es recurrir a algoritmos criptográficos, longitudes de clave y funciones hash adecuados. Dado que ese aspecto no ha sido armonizado a nivel europeo, los Estados miembros deben cooperar a fin de acordar algoritmos criptográficos, longitudes de clave y funciones hash para su utilización en el ámbito de las firmas y sellos electrónicos.

(9)

La adopción de la presente Decisión deja obsoleta la Decisión 2003/511/CE de la Comisión (2). Procede, por tanto, derogarla.

(10)

Las medidas previstas en la presente Decisión se ajustan al dictamen del Comité a que se refiere el artículo 48 del Reglamento (UE) n.o 910/2014.

HA ADOPTADO LA PRESENTE DECISIÓN:

Artículo 1

1.   En el anexo de la presente Decisión figuran las normas para la evaluación de la seguridad de productos de tecnología de la información que se aplican a la certificación de dispositivos cualificados de creación de firma electrónica o dispositivos cualificados de creación de sello electrónico de conformidad con el artículo 30, apartado 3, letra a), o con el artículo 39, apartado 2, del Reglamento (UE) n.o 910/2014, cuando los datos de creación de firma electrónica o los datos de creación de sello electrónico se conservan íntegramente, aunque no necesariamente de forma exclusiva, en un entorno gestionado por el usuario.

2.   Hasta que la Comisión establezca una lista de normas para la evaluación de la seguridad de los productos de tecnología de la información que se aplican a la certificación de dispositivos cualificados de creación de firmas electrónicas o dispositivos cualificados de creación de sellos electrónicos, cuando un prestador cualificado de servicios de confianza gestione los datos de creación de firma electrónica o los datos de creación del sello electrónico en nombre de un firmante o de un creador de un sello, la certificación de esos productos se basará en un proceso que, de conformidad con el artículo 30, apartado 3, letra b), haga uso de unos niveles de seguridad equivalentes a los exigidos por el artículo 30, apartado 3, letra a), y que sea notificado a la Comisión por el organismo público o privado a que se refiere el artículo 30, apartado 1, del Reglamento (UE) n.o 910/2014.

Artículo 2

Queda derogada la Decisión 2003/511/CE.

Artículo 3

La presente Decisión entrará en vigor a los veinte días de su publicación en el Diario Oficial de la Unión Europea.

Hecho en Bruselas, el 25 de abril de 2016.

Por la Comisión

El Presidente

Jean-Claude JUNCKER


(1)  DO L 257 de 28.8.2014, p. 73.

(2)  Decisión 2003/511/CE de la Comisión, de 14 de julio de 2003, relativa a la publicación de los números de referencia de las normas que gozan de reconocimiento general para productos de firma electrónica, de conformidad con lo dispuesto en la Directiva 1999/93/CE del Parlamento Europeo y del Consejo (DO L 175 de 15.7.2003, p. 45).


ANEXO

LISTA DE NORMAS A QUE SE REFIERE EL ARTÍCULO 1, APARTADO 1

ISO/IEC 15408 — Information technology — Security techniques — Evaluation criteria for IT security (Tecnología de la información — Técnicas de seguridad — Criterios de evaluación para la seguridad de la TI), Partes 1 a 3 enumeradas a continuación:

ISO/IEC 15408-1:2009 — Information technology — Security techniques — Evaluation criteria for IT security — Parte 1. (Tecnología de la información — Técnicas de seguridad — Criterios de evaluación para la seguridad de la TI. Parte 1). ISO, 2009.

ISO/IEC 15408-2:2008 — Information technology — Security techniques — Evaluation criteria for IT security — Parte 2. (Tecnología de la información — Técnicas de seguridad — Criterios de evaluación para la seguridad de la TI. Parte 2). ISO, 2008.

ISO/IEC 15408-3:2008 Information technology — Security techniques — Evaluation criteria for IT security — Parte 3 (Tecnología de la información — Técnicas de seguridad — Criterios de evaluación para la seguridad de la TI. Parte 3). ISO, 2008.

e

ISO/IEC 18045:2008: Information technology — Security techniques — Methodology for IT security evaluation (Tecnología de la información — Técnicas de seguridad — Metodología para la evaluación de la seguridad de la TI).

y

EN 419 211 — Protection profiles for secure signature creation device (Perfiles de protección para los dispositivos seguros de creación de firma), Partes 1 a 6 —en su caso— enumeradas a continuación:

EN 419211-1:2014 — Protection profiles for secure signature creation device — Part 1: Overview (Perfiles de protección para los dispositivos seguros de creación de firma. Parte 1: Generalidades).

EN 419211-2:2013 — Protection profiles for secure signature creation device — Part 2: Device with key generation (Perfil de protección para los dispositivos seguros de creación de firma. Parte 2: Dispositivo con generación de claves).

EN 419211-3:2013 — Protection profiles for secure signature creation device — Part 3: Device with key import (Perfil de protección para los dispositivos seguros de creación de firma. Parte 3: Dispositivo con importación de claves).

EN 419211-4:2013 — Protection profiles for secure signature creation device — Part 4: Extension for device with key generation and trusted channel to certificate generation application (Perfil de protección para los dispositivos seguros de creación de firma. Parte 4: Extensión para el dispositivo con generación de claves y comunicación confiada con aplicación de generación de certificado).

EN 419211-5:2013 — Protection profiles for secure signature creation device — Part 5: Extension for device with key generation and trusted channel to signature creation application (Perfil de protección para los dispositivos seguros de creación de firma. Parte 5: Dispositivo con generación de claves y comunicación confiada con aplicación de creación de firma).

EN 419211-6:2014 — Protection profiles for secure signature creation device — Part 6: Extension for device with key import and trusted channel to signature creation application (Perfil de protección para los dispositivos seguros de creación de firma. Parte 6: Dispositivo con importación de claves y comunicación confiada con aplicación de creación de firma).

Normas de evaluación de Prestadores de Servicios de Confianza Digital

By | #eIdAS, Acreditación, Evaluación de conformidad, Servicios de Confianza Digital, Sin categoría | No Comments

Hasta el 1 de julio de 2016 seguirá siendo válida la evaluación de Prestadores de Servicios de Certificación con arreglo a las normas ETSI TS 101 456, ETSI TS 102 042 y ETSI TS 102 023.

Desde esa fecha serán de aplicación los nuevos estándares europeos EN 319 411-1 (equivalente a la ETSI TS 102 042) y EN 319 411-2 (equivalente a la ETSI TS 101 456) para los Prestadores de Servicios de Certificación y EN 319 421 (equivalente a la ETSI TS 102 023) para los Prestadores de Servicios de Sellado de Tiempo.

Los Prestadores de Servicios de Certificación y los Prestadores de Servicios de Sellado de Tiempo son casos particulares de los Prestadores de Servicios de Confianza Digital. Otros servicios de Confianza Digital son los de Custodia de documentos electrónicos firmados electrónicamente, los de Entrega Certificada (eDelivery) y los de firma en la nube o firma en servidor.

Para los nuevos servicios todavía no se han publicado las normas de evaluación.

 

Requisitos de seguridad para Prestadores de Servicios de Confianza Digital

By | Evaluación de conformidad, Sin categoría | No Comments

La norma EN 319 401 establece las medidas de seguridad técnicas y irganizativas que deben cumplir los prestadores de servicios de confianza digital.

Este artículo es un breve estracto de tales requistos:

  • The TSP shall use trustworthy systems and products that are protected against modification and ensure the technical security and reliability of the processes supported by them. In particular:
  • The TSP shall control physical access to components of the TSP’s system whose security is critical to the provision of its trust services and minimize risks related to physical security. In particular:
    1. physical access to components of the TSP’s system whose security is critical to the provision of its trust services shall be limited to authorized individuals;
    2. controls shall be implemented to avoid loss, damage or compromise of assets and interruption to business activities;
    3. controls shall be implemented to avoid compromise or theft of information and information processing facilities; and
    4. components that are critical for the secure operation of the trust service shall be located in a protected security perimeter with physical protection against intrusion, controls on access through the security perimeter and alarms to detect intrusion
  • Appropriate security controls shall be in place for the management of any cryptographic keys and any cryptographic devices throughout their lifecycle.
  • The TSP’s system access shall be limited to authorized individuals.
    In particular:

    1. Controls (e.g. firewalls) shall protect the TSP’s internal network domains from unauthorized access including access by subscribers and third parties. Firewalls should also be configured to prevent all protocols and accesses not required for the operation of the TSP.
    2. The TSP shall administer user  access of operators, administrators and system auditors. The administration shall include user account management and timely modification or removal of access.
    3. Access to information and application system functions shall be restricted in accordance with the access control policy. The TSP system shall provide sufficient computer security controls for the separation of trusted roles identified in TSP’s practices, including the separation of security administration and operation functions. Particularly, use of system utility programs shall be restricted and controlled.
    4. TSP personnel shall be identified and authenticated before using critical applications related to the service.
    5. TSP personnel shall be accountable for their activities (e.g. retaining event logs).
    6. Sensitive data shall be protected against being revealed through re-used storage objects (e.g. deleted files) being accessible to unauthorized users.
  • All media shall be handled securely in accordance with requirements of the information classification scheme. Media containing sensitive data shall be securely disposed of when no longer required.
  • The TSP shall ensure an appropriate level of protection  of its assets including information assets. In particular, the TSP shall maintain an inventory of all information assets and shall assign a classification consistent with the risk assessment.
  • The TSP shall ensure that employees and contractors support the trustworthiness of the TSP’s operations. In particular:
    1. The TSP shall employ staff and, if applicable, subcontractors, who possess the necessary expertise, reliability, experience, and qualifications and who have received training regarding security and personal data protection rules as  appropriate for the offered services and the job function.
    2. TSP personnel should be able to fulfil the requirement of  “expert knowledge, experience and qualifications” through formal training and credentials, or actual experience, or a combination of the two. This should include regular (at least every 12 months) updates on new threats and current security practices.
    3. Appropriate disciplinary sanctions shall be applied to personnel violating TSP policies or procedures.
    4. Security roles and responsibilities, as specified in the TSP’s management security policy, shall be documented in job descriptions or in documents available to all concerned personnel. Trusted roles, on which the security of the TSP’s operation is dependent, shall be clearly identified. Trusted roles shall be named by the management and shall be accepted by the management and the person to fulfil the role.
    5. TSP personnel (both temporary and permanent) shall have job descriptions defined from the view point of roles fulfilled with segregation of duties and least privilege, determining position sensitivity based on the duties and access levels, background screening and employee training and awareness. Where appropriate, these shall differentiate between general functions and TSP specific functions. These should include skills and experience requirements.
    6. Personnel shall exercise administrative and management procedures and processes that are in line with the TSP’s information security management procedures.
    7. Managerial personnel shall possess experience or training with respect to the trust service that is provided, familiarity with security procedures for personnel with security responsibilities and experience with information security and risk assessment sufficient to carry out management functions.
    8. All TSP personnel in trusted roles shall be free from conflict of interest that might prejudice the impartiality of the TSP operations.
    9. Trusted roles shall include roles that involve the following responsibilities:
      • Security Officers: Overall responsibility for administering the implementation of the security practices.
      • System Administrators: Authorized to install, configure and maintain the TSP trustworthy systems for service management.
      • System Operators: Responsible for operating the TSP trustworthy systems on a day-to-day basis. Authorized to perform system backup and recovery.
      • System Auditors: Authorized to view archives and audit logs of the TSP trustworthy systems.
    10. TSP personnel shall be formally appointed to trusted roles by senior management responsible for security requiring the principle of “least privilege” when accessing or when configuring access privileges.
    11. Personnel shall not have access to the trusted functions until any necessary checks are completed.
  • Conflicting duties and areas of responsibility shall be segregated to reduce opportunities for unauthorized or unintentional modification  or misuse of the TSP assets.
  • The TSP shall carry out a risk assessment to identify, analyse and evaluate trust service risks taking into account business and technical issues.
  • The TSP  shall select the appropriate risk treatment measures, taking account of the risk assessment results. The risk treatment measures shall ensure that the level of security is commensurate to the degree of risk.
  • The TSP shall determine all security requirements and operational procedures that are necessary to implement the risk treatment options measures chosen as documented in the information security policy and the trust service practice statement.
  • The risk assessment shall be regularly reviewed and revised.
  • The TSP shall specify the set of policies and practices appropriate for the trust services it is providing. These shall be approved by management, published and communicated to employees and external parties as relevant.
  • The TSP shall have a statement of the practices and procedures for the trust service provided. In particular:
    1. The TSP shall have a statement of the practices and procedures used to address all the requirements identified for the applicable TSP policy.
    2. The TSP’s trust service practice statement shall identify the obligations of all external organizations supporting the TSP services including the applicable policies and practices.
    3. The TSP shall make available to subscribers and relying parties its practice statement, and other relevant documentation, as necessary to assess conformance to the service policy.
    4. The TSP shall have a management body with overall responsibility for the TSP with final authority for approving the TSP practice statement.
    5. The TSP management shall implement the practices.
    6. The TSP shall define a review process for the practices including responsibilities for maintaining the TSP practice statement.
    7. The TSP shall notify notice of changes it intends to make in its practice statement and shall, following approval by management, make the revised TSP practice statement immediately available to subscribers and relying parties.
    8. The TSP shall state in its practices the provisions made for termination of service
  • TSP shall make the terms and conditions regarding its services available to all subscribers and relying parties.
  • These terms and conditions shall at least specify for each trust service policy supported by the TSP the following:
    1. the trust service policy being applied;
    2. any limitations on the use of the service such as the expected life-time of public key certificates.
    3. the subscriber’s obligations, if any;
    4. information for parties relying on the trust service, such as how to verify the trust service token, any possible limitations on the validity period associated with the trust service token.
    5. the period of time during which TSP event logs are retained;
    6. limitations of liability;
    7. limitations on the use of the services provided including the limitation for damages arising from the use of services exceeding such limitations;
    8. the applicable legal system;
    9. procedures for complaints and dispute settlement;
    10. whether  the TSP’s trust service has been assessed to be conformant with the trust service policy, and if so through which conformity assessment scheme; and the TSP contact information.
  • Customers shall be informed about the limitations in advance.
  • Terms and conditions shall be made available through a durable means of communication. This information shall be available in a readily understandable language. It may be transmitted electronically.
  • The TSP shall define an information security policy which is approved by management and which sets out the organization’s approach to managing its information security. In particular:
    1. A TSP’s information security policy shall be documented, implemented and maintained including the security controls and operating procedures for TSP facilities, systems and information assets providing the services. The TSP shall publish and communicate this information security policy to all employees who are impacted by it.
    2. The TSP shall retain overall responsibility for conformance with the procedures prescribed in its information security policy, even when the TSP functionality is undertaken by outsourcers. TSP shall define the outsourcers liability and ensure that outsourcer are bound to implement any controls required by the TSP
    3. The TSP information security policy and inventory of assets for information security shall be reviewed at planned intervals or if significant changes occur to ensure their continuing suitability, adequacy and effectiveness. Any changes that will impact on the level of security provided shall be approved by the TSP high level management body. The configuration of the TSPs systems shall be regularly checked for changes which violate the TSPs security policies.
    4. A TSP’s management security policy shall be documented, implemented and maintained including the security controls and operating procedures for TSP facilities, systems and information assets providing the services.
  • The TSP organization shall be reliable. In particular:
    1. Trust service practices under which the TSP operates shall be non-discriminatory.
    2. The TSP shall make its services accessible to all applicants whose activities fall within its declared field of operation and that agree to abide by their obligations as specified in the TSP terms and conditions.
    3. The TSP shall maintain sufficient financial resources and/or obtain appropriate liability insurance, in accordance with national law, to cover liabilities arising from its operations and/or activities.
    4. The TSP shall have the financial stability and resources required to operate in conformity with this policy.
    5. The TSP shall have  policies and procedures for the resolution of complaints and disputes received from customers or other relying parties about the provisioning of the services or any other related matters.
    6. The TSP shall have a documented agreement and contractual relationship in place where the provisioning of services involves subcontracting, outsourcing or other third party arrangements.
  • Conflicting duties and areas of responsibility shall be segregated to reduce opportunities for unauthorized or unintentional modification  or misuse of the TSP assets.
  • The TSP shall ensure that employees and contractors support the trustworthiness of the TSP’s operations. In particular:
    1. The TSP shall employ staff and, if applicable, subcontractors, who possess the necessary expertise, reliability, experience, and qualifications and who have received training regarding security and personal data protection rules as  appropriate for the offered services and the job function.
    2. TSP personnel should be able to fulfil the requirement of  “expert knowledge, experience and qualifications” through formal training and credentials, or actual experience, or a combination of the two. This should include regular (at least every 12 months) updates on new threats and current security practices.
    3. Appropriate disciplinary sanctions shall be applied to personnel violating TSP policies or procedures.Security roles and responsibilities, as specified in the TSP’s management security policy, shall be documented in job descriptions or in documents available to all concerned personnel.
    4. Trusted roles, on which the security of the TSP’s operation is dependent, shall be clearly identified. Trusted roles shall be named by the management and shall be accepted by the management and the person to fulfil the role.
    5. TSP personnel (both temporary and permanent) shall have job descriptions defined from the view point of roles fulfilled with segregation of duties and least privilege (see clause 7.1.2), determining position sensitivity based on the duties and access levels, background screening and employee training and awareness. Where appropriate, these shall differentiate between general functions and TSP specific functions. These should include skills and experience requirements.
    6. Personnel shall exercise administrative and management procedures and processes that are in line with the TSP’s information security management procedures.
    7. Managerial personnel shall possess experience or training with respect to the trust service that is provided, familiarity with security procedures for personnel with security responsibilities and experience with information security and risk assessment sufficient to carry out management functions.
    8. All TSP personnel in trusted roles shall be free from conflict of interest that might prejudice the impartiality of the TSP operations.

i) Trusted roles shall include roles that involve the following responsibilities:
i) Security Officers: Overall responsibility for administering the implementation of the security practices.
ii) System Administrators: Authorized to install, configure and maintain the TSP trustworthy systems for service management.
iii) System Operators: Responsible for operating the TSP trustworthy systems on a day-to-day basis. Authorized to perform system backup and recovery.
iv) System Auditors: Authorized to view archives and audit logs of the TSP trustworthy systems.

j) TSP personnel shall be formally appointed to trusted roles by senior management responsible for security requiring the principle of “least privilege” when accessing or when configuring access privileges.
k) Personnel shall not have access to the trusted functions until any necessary checks are completed.
NOTE 9: In some countries it is not possible for TSP to obtain information on past convictions without the collaboration of the candidate employee.

 

The TSP shall ensure an appropriate level of protection  of its assets including information assets.
NOTE 1: See clause 8 of ISO/IEC 27002:2013 [i.3] for guidance.
In particular, the TSP shall maintain an inventory of all information assets and shall assign a classification consistent with the risk assessment.

All media shall be handled securely in accordance with requirements of the information classification scheme. Media containing sensitive data shall be securely disposed of when no longer required

 

The TSP’s system access shall be limited to authorized individuals.
In particular:
a) Controls (e.g. firewalls) shall protect the TSP’s internal network domains from unauthorized access including access by subscribers and third parties. Firewalls should also be configured to prevent all protocols and accesses not required for the operation of the TSP.
b) The TSP shall administer user  access of operators, administrators and system auditors. The administration shall include user account management and timely modification or removal of access.
c) Access to information and application system functions shall be restricted in accordance with the access control policy. The TSP system shall provide sufficient computer security controls for the separation of trusted roles identified in TSP’s practices, including the separation of security administration and operation functions. Particularly, use of system utility programs shall be restricted and controlled.
d) TSP personnel shall be identified and authenticated before using critical applications related to the service.
e) TSP personnel shall be accountable for their activities.
EXAMPLE: By retaining event logs.
f) Sensitive data shall be protected against being revealed through re-used storage objects (e.g. deleted files) being accessible to unauthorized users.

 

Appropriate security controls shall be in place for the management of any cryptographic keys and any cryptographic devices throughout their lifecycle

The TSP shall control physical access to components of the TSP’s system whose security is critical to the provision of its trust services and minimize risks related to physical security.

In particular:
a) physical access to components of the TSP’s system whose security is critical to the provision of its trust services shall be limited to authorized individuals;
NOTE 2: Criticality is identified through risk assessment, or through application security requirements, as requiring a security protection.
b) controls shall be implemented to avoid loss, damage or compromise of assets and interruption to business activities;
c) controls shall be implemented to avoid compromise or theft of information and information processing facilities; and
d) components that are critical for the secure operation of the trust service shall be located in a protected security perimeter with physical protection against intrusion, controls on access through the security perimeter and alarms to detect intrusion.

 

  • The TSP shall use trustworthy systems and products that are protected against modification and ensure the technical security and reliability of the processes supported by them.  In particular
    1. An analysis of security requirements shall be carried out at the design and requirements specification stage of any systems development project undertaken by the TSP or on behalf of the TSP to ensure that security is built into Information Technology’s systems.
      b) Change control procedures shall be applied for releases, modifications and emergency software fixes of any operational software.c) The integrity of TSP systems and information shall be protected against viruses, malicious and unauthorized software.
      d) Media used within the TSP systems shall be securely handled to protect media from damage, theft, unauthorized access and obsolescence.
      e) Media management procedures shall protect against obsolescence and deterioration of media within the period of time that records are required to be retained.
      f) Procedures shall be established and implemented for all trusted and administrative roles that impact on the provision of services.
      g) The TSP shall specify and apply procedures for ensuring security patches are applied within a reasonable time after they come available.  A security patch need not be applied if it would introduce additional vulnerabilities or instabilities that outweigh the benefits of applying the security patch. The reason for not applying any security patches shall be documented.

The TSP shall protect its network and systems from attack.
In particular:
a) The TSP shall segment its systems into networks or zones based on risk assessment considering functional, logical, and physical (including location) relationship between trustworthy systems and services. The TSP shall apply the same security controls to all systems co-located in the same zone.
b) The TSP shall restrict access and communications between zones to those necessary for the operation of the TSP. Not needed connections and services shall be explicitly forbidden or deactivated. The established rule set shall be reviewed on a regular basis.
c) The TSP shall maintain any elements of their critical systems (e.g. Root CA systems see ETSI EN 319 411-1 [i.12]) in a secured zone.
d) A dedicated network for administration of IT systems that is separated from the operational network shall be established. Systems used for administration shall not be used for non-administrative purposes.
e) Test platform and production platform shall be separated from other environments not concerned with live operations (e.g development).
f) Communication between distinct trustworthy systems shall only be established through trusted channels that are logically distinct from other communication channels and provide assured identification of its end points and protection of the channel data from modification or disclosure.
g) If external availability of the trust service is required, the external network connection to the internet shall be redundant to ensure availability of the services in case of a single failure. This may be achieved by two different network connections to one of more internet providers.
h) The TSP shall undergo or perform a regular vulnerability scan on public and private IP addresses identified by the TSP and record evidence that each vulnerability scan was performed by a person or entity with the skills, tools, proficiency, code of ethics, and independence necessary to provide a reliable report.
NOTE 1: See item 4c of the CA Browser Forum network security guide [i.8] for guidance regarding the time period.
i) The TSP shall undergo a penetration test on the TSP’s systems at set up and after infrastructure or application upgrades or modifications that the TSP determines are significant. The TSP shall record evidence that each penetration test was performed by a person or entity with the skills, tools, proficiency, code of ethics, and independence necessary to provide a reliable report.
NOTE 2: See item 4d of the CA Browser Forum network security guide [i.8] for guidance regarding the time period.

System activities concerning access to IT systems, user of IT systems, and service requests shall be monitored.
In particular:
a) Monitoring activities should take account of the sensitivity of any information collected or analysed.
b) Abnormal system activities that indicate a potential security violation, including intrusion into the TSP network, shall be detected and reported as alarms.
NOTE 1: Abnormal network system activities can comprise (external) network scans or packet drops.
c) The TSP IT systems shall monitor the following events:
i) Start-up and shutdown of the logging functions; and
ii) Availability and utilization of needed services with the TSP network.

d) The TSP shall act in a timely and co-ordinated manner in order to respond quickly to incidents and to limit the impact of breaches of security. The TSP shall appoint trusted role personnel to follow up on alerts of potentially critical security events and ensure that relevant incidents are reported in line with the TSP’s procedures.
e) The TSP shall establish procedures to notify the appropriate parties in line with the applicable regulatory rules of any breach of security or loss of integrity that has a significant impact on the trust service provided and on the personal data maintained therein.
NOTE 2: For TSPs operating within the European Union see Regulation (EU) No 910/2014 [i.2] Article 19.2 and contact the national supervisory body, or other competent authority for further guidance in implementing this article.
f) Where the breach of security or loss of integrity is likely to adversely affect a natural or legal person to whom the trusted service has been provided, the TSP shall also notify the natural or legal person of the breach of security or loss of integrity without undue delay.
g) Audit logs shall be monitored or reviewed regularly to identify evidence of malicious activity implementing automatic mechanisms to process the audit logs and alert personnel of possible critical security events.
NOTE 3: See clause 16 of ISO/IEC 27002:2013 [i.3] for guidance.
h) The TSP shall remediate within a reasonable period after the discovery of a critical vulnerability not previously addressed by the TSP. If this is not possible the TSP shall create and implement a plan to mitigate the critical vulnerability or the TSP shall document the factual basis for the TSP’s determination that the vulnerability does not require remediation.
NOTE 4: Further recommendations are given in the CA Browser Forum network security guide [i.8] item 4 f).
i) Incident reporting and response procedures shall be employed in such a way that damage from security incidents and malfunctions are minimized.

The TSP shall record and keep accessible for an appropriate period of time, including after the activities of the TSP have ceased, all relevant information concerning data issued and received by the TSP, in particular, for the purpose of providing evidence in legal proceedings and for the purpose of ensuring continuity of the service.
In particular:
a) The confidentiality and integrity of current and archived records concerning operation of services shall be maintained.
b) Records concerning the operation of services shall be completely and confidentially archived in accordance with disclosed business practices.
c) Records concerning the operation of services shall be made available if required for the purposes of providing evidence of the correct operation of the services for the purpose of legal proceedings.
d) The precise time of significant TSP environmental, key management and clock synchronization events shall be recorded. The time used to record events as required in the audit log shall be synchronised with UTC at least once a day.
e) Records concerning services shall be held for a period of time after the expiration of the validity of the signing keys or any trust service token as appropriate for providing necessary legal evidence and as notified in the TSP disclosure statement.
f) The events shall be logged in a way that they cannot be easily deleted or destroyed (except if reliably transferred to long-term media) within the period of time that they are required to be held.
EXAMPLE: This can be achieved, for example, through the use of write-only media, a record of each removable media used and the use of off-site backup.

In the event of a disaster, including compromise of the private signing key or trust service credentials, operations shall be restored as soon as possible. In particular, the TSP shall define and maintain a continuity plan to enact in case of a disaster.
NOTE 1: Other disaster situations include failure of critical components of a TSP trustworthy system, including hardware and software.
NOTE 2: See clause 17 of ISO/IEC 27002:2013 [i.3] for guidance.

Potential disruptions to subscribers and relying parties shall be minimized as a result of the cessation of the TSP’s services, and in particular continued maintenance of information required to verify the correctness of trust services shall be provided.
In particular:
a) The TSP shall have an up-to-date termination plan.
b) Before the TSP terminates its services at least the following procedures apply:
i) the TSP shall inform the following of the termination: all subscribers and other entities with which the TSP has agreements or other form of established relations, among which relying parties and TSP. In addition, this information shall be made available to other relying parties;
ii) TSP shall terminate authorization of all subcontractors to act on behalf of the TSP in carrying out any functions relating to the process of issuing trust service tokens;
iii) the TSP shall transfer obligations to a reliable party for maintaining all information necessary to provide evidence of the operation of the TSP for a reasonable period, unless it can be demonstrated that the TSP does not hold any such information; and
iv) TSP private keys, including backup copies, shall be destroyed, or withdrawn from use, in a manner such that the private keys cannot be retrieved;
v) where possible TSP should make arrangements to transfer provision of trust services for its existing customers to another TSP.
c) The TSP shall have an arrangement to cover the costs to fulfil these minimum requirements in case the TSP becomes bankrupt or for other reasons is unable to cover the costs by itself, as far as possible within the constraints of applicable legislation regarding bankruptcy.
d) The TSP shall state in its practices the provisions made for termination of service. This shall include:
i) notification of affected entities; and
ii) transferring the TSP obligations to other parties.
e) The TSP shall maintain or transfer to a reliable party its obligations to make available its public key or its trust service tokens to relying parties for a reasonable period.

The TSP shall ensure that it operates in a legal and trustworthy manner:
In particular:
a) The TSP shall provide evidence on how it meets the applicable legal requirements.
b) Trust services provided and end user products used in the provision of those services shall be made accessible for persons with disabilities.  Applicable standards such as ETSI EN 301 549 [i.13] should be taken into account.

c) Appropriate technical and organizational measures shall be taken against unauthorized or unlawful processing of personal data and against accidental loss or destruction of, or damage to, personal data.
NOTE: TSPs operating in Europe are required to ensure that personal data is processed in accordance with Directive 95/46/EC [i.1]. In this respect,  authentication for a service online concerns processing of only those identification data which are adequate, relevant and not excessive to grant access to that service online.