← All projects

STELAU / CERTIFICATE LIFECYCLE MANAGEMENT

reBopThe certificate.
Its entire lifecycle.

A certificate never stands alone. It has an issuer, usages, locations and an expiry date. reBop connects that information to make its lifecycle observable, understandable and manageable.

01 / A Stelau product

A pure-player CLM. Practical PKI expertise.

reBop is a Certificate Lifecycle Management platform, focused on certificates from discovery to observed renewal. It provides a cross-cutting view of public and private certificates beyond any single certification authority. Stelau applies its expertise in X.509, PKI infrastructures and operational constraints to the product.

01Discover02Read03Monitor04Correlate05Act
reBop / DashboardEnlarge
reBop dashboard with expiry indicators, annual chart and widget appearance settings.
DashboardDeadlines, distribution and customisable indicators bring the certificate estate into view.
reBop / Dashboard
reBop dashboard with expiry indicators, annual chart and widget appearance settings.

reBop interface screenshot · Press Escape to close.

02 / Discovery & collection

Inventory starts
where certificates live.

Internet, internal networks and local files: a useful inventory connects certificates with the places where they are observed. A filename or an expiry date is not enough.

Observe exposed services.

URLs and TCP ports, host lists, DNS exports or subdomain discovery provide several ways to locate certificates presented by accessible services.

Technical detail

Discovery sources include DNS searches and Certificate Transparency Logs. A CT result is evidence of issuance; observing a service reveals the certificate it actually presents.

Collect inside the infrastructure.

The reBop probe scans local filesystems and configured networks to discover certificates that are not exposed to the Internet.

Technical detail

The open-source probe runs on Windows, macOS, Linux and Unix. It produces a JSON file containing certificates and their context: local paths, hosts and IP addresses. Private key files are ignored.

Connect certificates to locations.

The same certificate may be used on multiple hosts or services. reBop retains its usage context to track renewals at each location.

Technical detail

File imports or probe uploads using an API key populate the inventory without confusing a certificate with the server using it. The probe remembers previously observed certificates to identify new ones.

reBop discovery and monitoring ↗How the probe works ↗

03 / Applied cryptography

Read the certificate.
Understand what it says.

Dates are only part of the story. An X.509 certificate carries an identity, a public key, usages and constraints. A CLM must make that information understandable.

X.509 / RFC 5280
Certificate ::= SEQUENCE {
  tbsCertificate     TBSCertificate,
  signatureAlgorithm AlgorithmIdentifier,
  signatureValue     BIT STRING
}

-- SubjectPublicKeyInfo, Validity,
-- Extensions: SAN, KU, EKU, AIA, CRL…
Certificate structure ↗

Read identities and usages.

Subject, issuer, serial number, validity period, public key and extensions: ASN.1 encoding provides access to the information describing a certificate.

SAN, KeyUsage, ExtendedKeyUsage, BasicConstraints, policies, AIA and CRL distribution points help explain the intended usage and environment of a certificate.

Examine the trust context.

reBop’s detailed analysis brings together certificate information, status and elements of its trust context, along with compliance analysis.

Product documentation covers inclusion in European eIDAS trusted lists, Mozilla and Microsoft. Adding a certificate to an inventory alone does not establish its trustworthiness for a particular use.

Prepare cryptographic agility.

Identifying signature algorithms, keys and usages helps prepare changes to cryptographic policies, including the post-quantum transition.

The first question is operational: where are the affected certificates, and which services depend on them? Inventory and parameter inspection reveal dependencies before a migration is planned.

reBop / X.509 analysisEnlarge
Detailed reBop certificate view with key usages, AKI, SKI and issuing authority information.
X.509 analysisKey usages, identifiers and authority information: explore the data beyond dates.
reBop / X.509 analysis
Detailed reBop certificate view with key usages, AKI, SKI and issuing authority information.

reBop interface screenshot · Press Escape to close.

The reBop certificate view ↗

04 / Renewal detection

A new certificate.
The right replacement?

A renewal links a previous certificate, a new certificate and their locations. reBop places that relationship at the centre of monitoring.

  1. 01

    A new observation reveals a certificate that may replace one already being monitored.

  2. 02

    The correlation engine, named AI Engine in reBop, identifies likely renewals and processes matches it considers sufficiently certain.

  3. 03

    Uncertain matches become proposals to accept or reject. Acceptance carries labels and monitoring settings over to the new certificate and archives the previous one.

  4. 04

    Continued observation of locations highlights expired, revoked or suspended certificates still online, and tracks the time between the start of validity and actual deployment.

reBop / Compare before decidingEnlarge
reBop renewal proposal comparing previous and new certificates, identities, locations and validity periods.
Compare before decidingA renewal proposal places both certificates side by side before acceptance or rejection.
reBop / Compare before deciding
reBop renewal proposal comparing previous and new certificates, identities, locations and validity periods.

reBop interface screenshot · Press Escape to close.

Deploy DelayStart of validity → observed deployment

Obtaining a renewed certificate and actually putting it into service are different steps. This delay highlights the gap between certificate availability and deployment. Detecting a renewal does not mean reBop automatically issues or deploys that certificate.

AI Engine ↗Renewals and Deploy Delay ↗

05 / Operations & oversight

The right information.
For the right action.

Reduce blind spots, organise deadlines and share decisions: technical understanding should lead to controlled operations.

reBop / The expiry timelineEnlarge
reBop timeline showing certificates approaching expiry by day and renewal statistics.
The expiry timelineAnticipate expirations and track renewals in a single chronological view.
reBop / The expiry timeline
reBop timeline showing certificates approaching expiry by day and renewal statistics.

reBop interface screenshot · Press Escape to close.

An actionable timeline.

The timeline groups certificates by expiry date and renewal status. Periods act as filters leading to the certificates requiring investigation.

In practice

Renewed certificates, pending renewals and remaining actions: the operational view helps teams prepare their work ahead of time.

Alerts that prompt action.

Validity, revocation and online-presence alerts, in-app notifications, emails and reports turn deadlines into information for the people concerned.

In practice

Periods and notifications are configurable. Alerts are tracked per user and organisation; available functions depend on the selected plan.

Shared operational context.

Labels, search and filters organise the inventory. Operator and viewer profiles distinguish operational management from consultation.

In practice

Logs record imports, certificate lifecycle events, label changes and decisions on renewal proposals; the initiating user is recorded where relevant.

Timeline ↗Profiles and logs ↗

06 / Deployment architecture

Your CLM, in
your environment.

SaaS.

A hosted platform for centralised monitoring. Probes report certificates from internal environments within their configured scope.

One view of exposed, internal and imported certificates.

In your infrastructure.

The Enterprise offering supports on-premise installation, virtual machines or containers, as well as deployment in your own IaaS.

Deployment arrangements and required features are scoped with the Stelau team.

Plans and deployment options ↗

07 / Your turn to explore

Your certificate.
Your bytes. Your browser.

This Stelau workshop adapts our React application built on Lapo Luchini’s ASN.1 decoder. Import a certificate or try the fictional example: X.509 fields, the ASN.1 tree and bytes stay synchronised with each selection.

ASN.1 AtelierLocal processing · no upload

Open a certificate or ASN.1 structure

PEM · DER · Base64 · Hex · drag & drop
One object, up to 256 KiB
30 → ASN.1 → X.509

From fields to bytes: explore identities, validity, usages, extensions and QCStatements.

This decoder reads the data. It does not validate signatures, trust paths, revocation or eIDAS qualification. No OCSP or CRL requests are made.

Objects remain in memory until cleared or the page is closed.Lapo Luchini · ASN.1ISC

The example is a self-signed demonstration certificate for fictional names. Its QCStatements demonstrate the encoding and do not confer any qualification. This workshop runs independently of the reBop service.

Documentation and technical references
Discovery and monitoringOpen-source probeCertificate analysisAI Engine and renewalsDeploy Delay and alertsTimelineProfiles and logsPlans and deployment

Let’s discuss your
certificate estate.

Talk to Stelau’s experts

Find what interests you.

Expertise, projects and articles. Escape to close.