How should certificate authorities handle certification audit evidence under ETSI EN 319 411-1?
Start with the audit boundary. The evidence file should identify the TSP or CA service being assessed, the applicable certificate policy, the CPS version, the certificate profiles and policy OIDs in use, the assessment period, and whether registration, certificate generation, dissemination, revocation management, revocation status, and subject-device provisioning are in scope.
Then map the file to requirement identifiers and operating records. EN 319 411-1 uses requirement IDs such as REG, GEN, REV, CSS, DIS, SDP, and OVR, and Annex B points to the conformity assessment checklist. An assessor should be able to follow each sampled requirement from the CP/CPS commitment to the retained record that proves operation during the assessment period.
- Keep a scope sheet naming the CA hierarchy, certificate policies, certificate profiles, repository locations, revocation-status methods, RAs, outsourced components, and excluded services.
- Trace each evidence request to the CP/CPS clause, EN 319 411-1 requirement ID, assessed period, record owner, evidence location, and sampling result.
- Separate public CP/CPS and terms from confidential procedure evidence; EN 319 411-1 allows sensitive operational detail to remain outside the published CPS.
- Record open findings with the affected requirement, evidence gap, corrective-action owner, and retest evidence rather than closing them with a certification label alone.
Supports using the CP, CPS, service components, requirement identifiers, and Annex B checklist as the structure for audit evidence.
Clause 7.10 supports retaining accessible, confidential, integrity-protected operational records for evidence and service continuity.