intelligence_src_823f7b237762257237
- Source-provided label
- Publisher RSS metadata
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Apr 14, 2015 00:00 UTC
- Retrieved
- Oct 14, 2026 00:12 UTC
ISRG has engaged the NCC Group Crypto Services team to perform a security review of Let’s Encrypt’s certificate authority software, boulder, and the ACME protocol. NCC Group’s team was selected due to their strong reputation for cryptography expertise, which brought together Matasano Security, iSEC Partners, and Intrepidus Group. The NCC Group audit will take place prior to the general availability of Let’s Encrypt’s service, and is intended to provide additional assurance that our systems are secure. The NCC Group audit does not replace the WebTrust audit, which will happen after general availability. “I’m very much looking forward to the general availability of Let’s Encrypt - lowering the bar both technically and financially for people to deploy TLS will result in a more encrypted Internet that helps increase security and preserve people’s privacy,” said Tom Ritter, Practice Director, NCC Group. Let’s Encrypt’s certificate authority software is called boulder. It’s largely written in the go language and makes use of CloudFlare’s CFSSL tools, which are also written in go. Our boulder software contains modules including a web front-end and registration, validation, certificate, and storage authorities. ACME, short for Automated Certificate Management Environment, is the protocol that Let’s Encrypt will use for automatic certificate issuance and management. We hope to standardize ACME in the IETF, starting with the formation of a working group later this year.
b096fa159e3854d7019846932d6ed0c8ace9be384fdb88c9a9f8eda37cf93c05Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 0 unverified.
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.