Cleverbase states it configured its systems so that the affected eMudhra certificates are no longer trusted.
Working securely through a week of incidents in the digital chain ↗ · repeat of an earlier article
What happened
- Cleverbase states its eIDAS and PKIoverheid certificates were not affected by the eMudhra incident.
- Cleverbase states one of its systems runs on PHP and was switched off until the security update was installed.
- Cleverbase states some applications took longer than usual because of extra manual checks.
Why it matters to Signicat
- Incident response disclosure by a Dutch QTSP-linked identity competitor; no commercial claim is made about Signicat.
Evidence from the source (4 quotes)
- “Moreover, the eIDAS certificates and PKIoverheid certificates we build on were not affected.” source ↗
- “One of our systems runs on PHP. It had only a limited impact on our services, but we still switched it off immediately, until the security update was installed.” source ↗
- “Because of the extra checks, some applications did take a little longer than usual.” source ↗
- “We are glad that our services remained available throughout the whole period.” source ↗
eSign trust servicesSecurity incidentThought leadershipBenelux
4 of 4 facts verified against the source · confidence medium · claude-haiku-5-5