The Public Notices First
A broken certificate on a payment, licensing, or public records page can trigger a browser warning. People may question whether the site is safe, contact the help desk, or abandon the service.
Tracking expiration dates is only the beginning. CertGov enforces certificate policies before issuance, routes requests for approval when required, and maintains a tamper-evident record of every decision.
Clear policies. Accountable decisions. Certificate visibility across departments.
A digital certificate helps prove that a website or service is authentic and protects information exchanged with it. Every certificate has an expiration date.
That date is getting closer. The maximum lifetime of a publicly trusted website certificate is being reduced in stages. By 2029, a certificate will need replacing far more frequently than under the previous 398-day maximum.
If a certificate expires, the public may see a security warning instead of the servie they need. A permit portal, payment page, or public records form can become unavailable at exactly the wrong time. Most teams will need to manage this increased workload with the staff and budgets they already have.
These limits apply to publicly trusted website (TLS) certificates. They do not apply to every kind of digital certificate.
Certificates are created by different people, in different departments, over many years. When one expires or needs to be changed, teams may discover too late that nobody has the complete picture.
A broken certificate on a payment, licensing, or public records page can trigger a browser warning. People may question whether the site is safe, contact the help desk, or abandon the service.
Handling renewals by hand takes time, and mistakes are easy to make. As certificate lifetimes get shorter, the work repeats more often across the agency's systems.
Departments may track their own certificates in spreadsheets or rely on individual staff knowledge. When someone changes roles or leaves, important information can leave with them.
A team may create a certificate to solve an immediate problem outside the normal process. Without visibility and policy controls, those certificates can remain unknown to the people responsible for oversight.
Reviewers may ask who requested a certificate, who approved it, and what happened afterward. Reconstructing the answers from email and disconnected records takes time.
Older systems and isolated networks may not be able to use services that need to communicate with external systems. Agencies need deployment options that account for those environments.
Different departments. Different systems. One need for clear, centralized certificate governance.
Most teams can eventually build a calendar reminder or spreadsheet. The harder questions are whether a certificate should have been issued in the first place — and whether the organization can prove who made that decision and why.
Set rules for permitted domains, certificate authorities, certificate types, key requirements, and maximum validity. Requests are evaluated against the matching profile, and sensitive requests can require human approval.
Certificate requests, approvals, rejections, and renewals are recorded in a tamper-evident log. Search by department, person, event, or date, and export records when reviewers ask.
The rules define what's allowed. The record shows what happened.
CertGov provides one place to govern certificate activity across departments and systems. It works alongside supported certificate providers and tools, so agencies can add consistent controls without assuming they need to rebuild their infrastructure.
Define permitted domains, certificate providers, certificate requirements, and validity limits. Evaluate requests against those rules and prevent requests that do not meet the defined requirements from proceeding.
Require approval for selected requests, collect a reason, and prevent requesters from approving their own requests. Approvers can respond through supported channels, including Slack, Teams, Webex, Zoom, or email.
Record certificate requests, approvals, rejections, and renewals in a tamper-evident log. Search activity by department, person, event, or date, and export records to CSV or JSON.
Discover certificates across supported websites and systems, then distinguish those that are tracked and managed, found but not yet managed, or outside defined governance rules.
Auditors and oversight bodies ask the same basic questions, whether the standard is the NIST Cybersecurity Framework 2.0, FISMA, or an agency's own policy: What are the rules? Who is responsible? Show me the record.
With CertGov, those answers don't have to be a scavenger hunt through email. Policies are defined and enforced, approvals are connected to requests, and certificate activity can be searched and exported.
CertGov supports your compliance work. It does not make an organization compliant on its own.
Cities, counties, state agencies, and school districts rarely have one central team doing everything. CertGov supports a more structured model for managing access and governance across separate teams.
Each department, agency, or campus can have its own organization and data, while central IT maintains broader visibility.
Create a standard foundation for policies and alerts, then apply it across additional departments or sites as appropriate.
Assign viewer, approver, or admin access based on responsibilities, and revoke access when people change roles or leave.
Give contractors access appropriate to their work while keeping the organization in control of its own data.
A certificate authority (CA) is the organization that issues certificates. Public sector teams may use publicly trusted providers for resident-facing websites and internal certificate authorities for systems behind the firewall.
CertGov provides a governance layer for supported provider integrations and certificate workflows. You do not need to assume every certificate comes from the same source.
Supported public providers include DigiCert and Sectigo. Internal and on-premises certificate authority workflows can also be governed, with exact support depending on the provider and configuration.
In the cloud. Choose where your data lives: US East or EU West. The two regions are fully separate from each other.
On your own servers. CertGov can run inside your network on a Linux server with a PostgreSQL database. The self-hosted deployment can support air-gapped environments with an offline certificate authority.
Your data stays yours. Each organization keeps control of its own data. Some integrations require connectivity, so available features depend on the deployment and configuration.
Renewing certificates by hand becomes increasingly difficult as publicly trusted TLS certificates move toward 47-day maximum lifetimes. CertGov supports automated renewal and installation workflows while continuing to apply defined policies and approval requirements.
CertGov supports ACME, Kubernetes integrations, REST APIs, and an open-source agent for installing certificates on Windows and Linux applications and supported network equipment such as F5 BIG-IP.
For technical teams, supported workflows include ACME clients such as certbot, acme.sh, Caddy, and Traefik; cert-manager for Kubernetes; DNS validation using direct credentials or CNAME delegation; and token-scoped REST APIs.
Set alerts at the intervals that make sense for your organization and send them to the people responsible for each service. A timely notification that reaches the right owner can help prevent an avoidable certificate outage.
CertGov helps discover digital certificates, checks new requests against defined rules, routes requests for approval when required, maintains records of certificate activity, and supports automated certificate workflows.
Many tools focus on finding certificates and warning before they expire. CertGov also focuses on policy enforcement before issuance and a tamper-evident record of decisions and activity — capabilities that matter when public sector teams need to demonstrate oversight and accountability.
Shorter lifetimes limit how long a certificate remains valid if it is compromised or misused, and encourage more consistent automated renewal. The maximum lifetime for publicly trusted TLS certificates is scheduled to reach 47 days on March 15, 2029.
CertGov supports separate organizations and role-based access for teams, with central visibility across supported departmental environments. The exact setup depends on your organization's configuration.
The self-hosted version can run on a Linux server with a PostgreSQL database and can support air-gapped environments with an offline certificate authority. Some integrations require connectivity, so available features depend on your setup.
CertGov supports internal and on-premises certificate authority workflows. Exact support depends on the certificate authority and your environment, so the team should confirm compatibility with your specific setup.
CertGov supports viewer, approver, and admin roles. You can assign access based on the contractor's responsibilities and revoke it when the work ends.
CertGov maintains a tamper-evident record of certificate requests, approvals, rejections, and renewals. Records can be searched and exported in CSV or JSON.
No single tool makes an organization compliant. CertGov provides policies, approvals, visibility, and records for the certificate portion of your broader security and compliance program.
CertGov supports automated renewal and installation workflows through ACME, Kubernetes integrations, and the CertGov Agent, while keeping defined rules and approval requirements in the process. This can reduce routine manual work while preserving oversight.
No. CertGov is designed to work alongside supported certificate providers, tools, and processes, adding a governance layer rather than requiring every environment to use identical infrastructure.
Talk with us about how CertGov's policies, approvals, and audit trails could work across your departments, systems, and review processes.
Talk to Our Team