Document control

AreaISM
Procedure status

DRAFT

OwnerCSIRT
ApproversOMB
Approval status

APPROVAL REQUIRED

Approved version and date


Statement

This procedure describes what should be done by the EGI CSIRT in the event of a compromised identity certificate, including long lived certificates and proxies. This applies to robot certificates and service certificates as well as user certificates. This also includes what is done when certificates are linked to security incidents. This procedure also addresses usage of Central Security Emergency suspension. The implications of a CA compromise are also briefly described.

Dissemination Level

TLP:WHITE - Public

Procedure reviews

The following table is updated after every review of this procedure.

DateReview bySummary of resultsFollow-up actions / Comments

 

Baptiste Grenier 

Import form EGI wiki




Table of contents

Overview

The EGI Software Vulnerability issue handling procedure is described in EGI Documents: EGI CSIRT Operational Procedure for Compromised Certificates and Central Security Emergency suspension.

Definitions

Please refer to the EGI Glossary for the definitions of the terms used in this procedure.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Entities involved in the procedure

Triggers

Steps

See EGI Documents: EGI CSIRT Operational Procedure for Compromised Certificates and Central Security Emergency suspension.