Certificates never live in isolation — they sit on hosts, in cloud APIs, in load balancers, and in Kubernetes clusters. TigerTrust’s infrastructure inventory tracks all of these as first-class objects so scans, deployments, and audits can reference them by name rather than by IP.
Infrastructure

​
What it is

Infrastructure is where you register the physical and virtual machines, cloud accounts, and field agents that TigerTrust manages. Everything else in the platform — discovery scans, deployment targets, and audit entries — references these inventory objects.

​
When to use it

  • Register a new data center host so you can run discovery scans against it.
  • Add an AWS or Azure account so TigerTrust can enumerate its certificate services.
  • View the list of registered field agents and their last heartbeat before triggering a scan.
  • See aggregate scan coverage: how many hosts have been scanned and how many certificates were found.

​
The three resource types

Hosts

Physical or virtual machines where certificates live and where a field agent may run. Auto-registered on first agent check-in.

Cloud accounts

AWS accounts, Azure subscriptions, or GCP projects — the authorization envelope for cloud-native scans and deployment.

Agents

Field agents that TigerTrust registers, tracks, and dispatches tasks to. Each agent shows status, capabilities, last heartbeat, and version.

​
Set it up

1

Register a host

Go to Infrastructure > Hosts and click Add host. Enter the hostname, IP address, OS type, and optional cloud provider. Hosts can also auto-register when a field agent connects for the first time.
2

Register a cloud account

Go to Infrastructure > Cloud accounts and click Add account. Select the provider (AWS, Azure, or GCP), enter the account/subscription/project identifier, and choose the authentication method. For day-to-day cloud discovery, most operators use Cloud integrations instead — cloud accounts are the lower-level primitive used for identity and role-based access.
3

Register a field agent

Go to Infrastructure > Agents and click Add agent. Follow the agent setup wizard, which generates an installation command for your target host. After running the command, the agent appears in the list within a minute.

​
What you’ll see

Infrastructure > Agents shows each registered agent with its hostname, status (active, inactive, unhealthy), capabilities (discovery, deploy, ssh, tpm), last heartbeat, and binary version. The status strip at the top of Infrastructure shows total scan count, active scans, total certificates found, and certificates imported into managed inventory.

​
One-click filesystem scans

For common on-disk trust stores, Infrastructure provides preset scan types you can kick off without authoring raw scan payloads:
  • Windows Certificate Store
  • macOS Keychain
  • Linux /etc/ssl/certs
  • Java KeyStore / PKCS#12
Each of these creates a discovery scan of the filesystem type and dispatches it to the selected agent.

Discovery

Scan types, lifecycle, and importing results.

Cloud integrations

Register AWS, Azure, and GCP accounts and set required permissions.

Agents and Collector

How agents authenticate, poll tasks, and report results.