Skip to content

Logging and Monitoring

Effective logging and monitoring are critical for transparency, security, and compliance within the EUDI Wallet Ecosystem. The following guidance distinguishes between sandbox and production environments.

Sandbox Logging

Purpose:
To support troubleshooting, integration testing, and conformance validation without handling live personal data.

Best Practices:

  • Log only pseudonymized or synthetic data.
  • Record all OpenID4VP and OpenID4VCI message exchanges for test sessions.
  • Include timestamps, request IDs, and status codes, trace ID, for each transaction.
  • Capture cryptographic validation results (e.g., signature verification success/failure).
  • Avoid storing wallet identifiers or end-user personal data.
  • Rotate logs frequently (e.g., daily) and purge automatically after 14–30 days.
  • Provide structured log export (JSON).

Production Logging

Purpose:
To ensure service reliability, detect anomalies, and support audits — while maintaining GDPR and ARF compliance.

Key Principles:

  • Data Minimization: Log only what is strictly necessary for operational or security purposes.
  • Pseudonymization: Replace or hash any user identifiers before storage.
  • Purpose Limitation: Logs may only be used for security, audit, or compliance purposes — not profiling or analytics.
  • Storage Limitation: Retain logs for the minimum period required (e.g., 90 days operational, 12 months audit).
  • Access Control: Restrict access to authorized DevOps and compliance personnel only.
  • Integrity & Confidentiality: Protect logs using encryption in transit (TLS 1.3) and at rest (AES-256).
  • Traceability: Maintain a verifiable chain of custody for all log archives.
  • Incident Reporting: Log security-related events in real-time to the Orchestrator’s incident interface.

Recommended Data Points:

  • Timestamp and unique transaction/session ID
  • Request type (presentation/issuance)
  • Wallet invocation method (deeplink, QR, API)
  • Cryptographic validation outcome (success/failure, certificate used)
  • Error or exception messages (without sensitive payloads)
  • System performance metrics (latency, uptime, throughput)

Sandbox Monitoring

Objective:
Monitor integration health and readiness for compliance certification.

Recommended Metrics:

  • API responsiveness and uptime
  • Request/response validation rate
  • Credential format interoperability (SD-JWT vs mDoc)
  • Wallet invocation success ratio
  • Transaction pass/fail rates

Production Monitoring

Objective:
Ensure ongoing trustworthiness, performance, and security of the RP’s integration in compliance with GDPR and ARF operational guidelines.

Recommended Metrics:

  • Service uptime (target ≥ 99.9%)
  • Average response time and load latency
  • Presentation success rate per credential format
  • Error rates by category (validation, cryptographic, transport)
  • Certificate validity and expiration tracking
  • Real-time security event alerts (e.g., replay attempts, unauthorized access)

Monitoring Practices:

  • Deploy a secure, privacy-preserving monitoring solution with centralized observability (e.g., Prometheus + Grafana).
  • Anonymize event identifiers before transmission to third-party monitoring services.
  • Configure automated alerts for expiring Access/Registration Certificates.
  • Support incident notification and trust status reporting to the Orchestrator.
  • Document monitoring responsibilities in the RP’s Data Protection Impact Assessment (DPIA).