mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-30 14:57:36 +00:00
zeekay
db49f40b8e
Public-facing docs, metadata, and branding: - README.md: remove fork attribution, rebrand intro - package.json: clean description - CONTRIBUTING.md, SECURITY.md: remove Infisical mentions - LLM.md: update image name, remove fork language - docs/docs.json: rebrand name, nav labels, social links, footer URLs - company/ handbook & docs: rebrand all Infisical mentions - .env.migration.example: use hanzokms credentials - flake.nix: update description, remove infisical package - .github/ISSUE_TEMPLATE/config.yml: fix broken ghcr.io URLs - docs/ (24 files): rebrand prose, mermaid diagrams, API URLs - docs/Dockerfile: update spec fetch URL Removed upstream assets: - img/infisical_github_repo.png, infisical_github_repo2.png - .github/images/star-infisical.gif - .github/images/.!35663!deploy-to-aws.png (corrupted empty) NOT changed (would break code/legal): - LICENSE (MIT copyright must stay) - backend/src/ee/LICENSE.md (upstream enterprise license) - backend/package.json (@infisical/* npm deps) - Dockerfiles (apt-get install infisical CLI) - env var names (INFISICAL_TOKEN, INF_APP_CONNECTION_*) - docs.json page paths (require file renames) - frontend/dist/locales (compiled translation keys)
42 lines
2.1 KiB
Plaintext
42 lines
2.1 KiB
Plaintext
---
|
|
sidebarTitle: "Overview"
|
|
description: "Learn how to discover certificates across your infrastructure with KMS"
|
|
---
|
|
|
|
Certificate Discovery enables automated scanning of your infrastructure to find certificates. By configuring discovery jobs, you can continuously monitor for certificates deployed across your environment, giving you full visibility into your organization's certificate landscape.
|
|
|
|
## Concept
|
|
|
|
Discovery jobs scan your infrastructure for certificates and organize the results as **installations**, unique locations where certificates were found. Each installation tracks the certificates discovered at that location across multiple scans, allowing you to monitor certificate changes over time.
|
|
|
|
## Discovery Types
|
|
|
|
KMS supports multiple discovery types, each targeting a different source of certificates:
|
|
|
|
- **[Network](/documentation/platform/pki/discovery/network)**: Scans network endpoints over TLS to discover certificates served by hosts across IP ranges and domains.
|
|
|
|
<Note>
|
|
Additional discovery types will be added in future releases.
|
|
</Note>
|
|
|
|
## Installations
|
|
|
|
An installation represents a unique location where a certificate was discovered.
|
|
|
|
<Note>
|
|
For Network discovery, each installation is identified by its hostname or IP address and port combination.
|
|
</Note>
|
|
|
|
Installations can be viewed from the **Installations** tab on the Discovery page, or from the detail page of a specific discovery job. You can also view installations associated with a specific certificate from the certificate's detail page.
|
|
|
|
## FAQ
|
|
|
|
<AccordionGroup>
|
|
<Accordion title="How are discovered certificates matched to existing certificates?">
|
|
Discovered certificates are matched by their fingerprint. If a discovered certificate matches an existing certificate in your KMS project, the installation will be linked to that certificate.
|
|
</Accordion>
|
|
<Accordion title="What happens when a certificate changes at an endpoint?">
|
|
When a subsequent scan detects a different certificate at a location, the installation is updated to reflect the new certificate. The previous certificate association is preserved in the scan history.
|
|
</Accordion>
|
|
</AccordionGroup>
|