Free operations template

Build a useful credential inventory without collecting secrets.

A clean CSV for mapping ownership, expiry, and rotation policy. Use it on its own today, then import it into KeyGuardRail when you are ready.

Import-compatible

Start with the operational facts.

The file uses KeyGuardRail’s exact import header and includes three clearly fictional examples you can replace.

Name	Provider	Type	Environment	Owner	Next signal
Stripe production	Stripe	API key	Production	Payments platform	Expires Dec 15
GitHub deploy app	GitHub	OAuth client	Production	Platform engineering	Rotate in 90 days
AWS backup role	AWS	Access key	Production	Infrastructure	Rotate in 90 days

Field guide

Keep the sheet useful to operators and safe to share with the people coordinating lifecycle work.

01name

A recognizable system label—not the credential value.

02provider

The cloud, SaaS platform, vault, or internal issuer.

03credential_type

API key, access key, certificate, OAuth client, service account, token, or other.

04environment

Production, staging, development, or shared.

05owner

The accountable team or person who can coordinate rotation.

06expires_on

The provider expiry date in YYYY-MM-DD format, when one exists.

07last_rotated_on

The last confirmed rotation date in YYYY-MM-DD format.

08rotation_interval_days

Your policy interval, such as 90 or 365 days.

09runbook_url

An HTTPS link to the authorized rotation procedure.

Keep outside the sheet

From sheet to control plane

KeyGuardRail imports this file atomically, calculates the earliest lifecycle deadline, and keeps every follow-up attached to an owner.

The imported schema has no secret-value field.