Let’s Encrypt for Companies with KeyChest

Category : https , keychest , letsencrypt

Unifying Let’s Encrypt and Long-term Certificates

Let’s Encrypt has a number of downsides when used on a large scale. It uses modern key management protocols, but the high-level of automation requires management. This is what KeyChest provides.

Each blue box can be just one click.

The “zero” cost of Let’s Encrypt certificates is balanced-out with two main downsides: rate limits and short lifetime of certificates. While it’s great to get a free product, it becomes somewhat dangerous when you start relying on it without giving a proper thought to what should happen in 3 months’ time when you need to renew it.

There is also an adoption barrier as Let’s Encrypt uses an automation for renewals (so called ACMEv2 standard) and it requires a complete change in the way you manage your certificates.

Nevertheless, Let’s Encrypt is a viable option for HTTPS and other encrypted internet services.

The US government has been using Let’s Encrypt on its gateways for some time now – a list of domains from just one such certificate.

There are many instances where operational teams choose to deploy a Let’s Encrypt certificate when an important service went down due to an expired certificate or the time left is too short to follow usual purchasing. Now imagine you have hundreds such certificates – how can you keep on top of them all?

KeyChest is now testing (Dec 2019) a new proxy service, which provides a valuable information about the status of Let’s Encrypt certificates. The use requires a small change to the way you use KeyChest agents – Certbot by setting an HTTPS_PROXY. If your existing command is “certbot renew”, the new version would be:

“export HTTPS_PROXY=https://test.keychest.net:6443; certbot renew”

KeyChest will start logging all your requests and create statistics of your usages of Let’s Encrypt. You will instantly get information about the activity of your Certbot agents and detect issues when they happen – not when your certificates start expiring.

This also helps to comply with Let’s Encrypt rate limits, some of which are fairly strict:

  1. maximum of 5 new certificates per domain per week;
  2. 50 certificates per registered domain per week;
  3. 300 new “orders per account per 3 hours; or
  4. 5 failed validations per account per hour.

Deep Let’s Encrypt Proxy

While the monitoring will get you on top of your Let’s Encrypt usage and reduce the risk of downtimes. Our ambition is to unify ACME and “legacy” certificate issuers.

We achieve that with a deep proxy that does the actual communication with the Let’s Encrypt issuing servers and also validation challenges.

This allows us to forward certificate requests to Let’s Encrypt, Comodo, Symantec, … or any other certificate issuer according to your requirements. To further simplify your IT operations, our proxy architecture allows endpoint agents to be much smaller with fewer dependencies and installation issues.

Keychest agent – one internal proxy per network, is a single gateway with an access control to minimize any new additional risk.

You can either forward (an HTTP reverse proxy) validation requests directly to the KeyChest service, or use our lightweight agents available to the Small Enterprise customers.

Many companies are considering switching to Let’s Encrypt. What we offer is a management service to keep your commercial certificates while simplifying the configuration of your servers and preventing downtimes.

KeyChest has a complete database of all internet certificates and can automatically start monitoring any new servers and services you create – providing you with ongoing 100% coverage of your registered domains.

KEYCHEST and HTTPS automation

KeyChest started as a simple HTTPS monitoring service. It has had its own database of all web certificates for about a year. And it helped issue first real certificates this week.

“Read More”

A story of building a service (KEYCHEST)

Category : security

I have written this for KeyChest (https://keychest.net) users and some encouraged me to re-post. If you want to start a company, you may find a few lessons in it. If you like what I’m trying to build or even want to help, let me know – dan (at) keychest.net

“Read More”

Security of Sensor Networks (2008)

Category : key management , security

The WINES Infrastructure project deployed wireless sensor networks to monitor large bridges (Humber bridge), tunnels (London Underground), and water systems. Our task in the project was to perform a detailed analysis of security issues in existing hardware and software platforms for wireless sensor networks.

“Read More”

Trusted Path for Smart Cards

Category : passwords , security

The main problem with smart cards is lack of secure display and keyboard that would allow users to verify data sent to the smart card from their computer. Malware on the computer may then alter the data and, for example, change the recipient of a bank transfer.

“Read More”

Privacy in Common Criteria

Category : security

Still at Cambridge Uni, Vashek Matyas and myself looked at the definition of privacy in the Common Criteria standard. With Snowden and Echelon some years later, our definitions of unlikable anonymity and pseudonymity make even more sense.

“Read More”

Chrysalis Luna CA3

Category : key management , security

I moved some of the contents from an old website of mine. This is one of a small projects back from my time at the University of Cambridge, where we hacked a Chrysalis Luna CA3, which would now be part of SafeNet HSM portfolio.

“Read More”

Minerva Attack and Humble Beginnings

Category : crypto , security

Masaryk University has published a new cryptographic attack. You may still remember their ROCA attack from 2017. While ROCA was about the RSA encryption, MINERVA is about Elliptic Curve (ECC) signing.

“Read More”

Web Encryption – Punishment of SMBs by Tech Giants?

Mandating use of HTTPS / SSL certainly seems to have something in common with security certifications like FIPS140-2 or Common Criteria. Very few understand how it really helps, how complex it is but many already know how costly it can be.

“Read More”

Monzo and Challenger Banks’ Security

Category : governance , payments , security

Earlier today I read an article about Monzo leaking PINs of their customers into operational logs. Bad. What’s worse – this is the second Monzo’s technical problem I came across within last 12 months.

“Read More”