Philippines staffing guide · Published
On this page
Build a credential expiry register for remote admin accounts
A practical register for tracking password, key, certificate, and domain expiries across remote administrative accounts without centralizing secrets.
Remote administrative work depends on accounts, keys, certificates, and domains that all expire on different schedules. When the expiry dates live only in someone's memory, a routine Tuesday can turn into an outage or a rushed credential reset. A credential expiry register records what expires, who owns it, and how it is renewed without storing the secret itself. The register is a calendar and a responsibility map, not a password vault.
The assistant can maintain the register, send reminders, and prepare the renewal steps for the owner. The owner performs high-risk rotations and approves any change that affects production access. That split keeps the register useful without concentrating authority in one remote role. It also makes offboarding faster because every account has a named owner and a known renewal path.
Inventory every credential that expires
List passwords for admin panels, API keys, signing certificates, OAuth refresh tokens, domain registrations, and any service account with a renewal date. Include credentials that technically do not expire but should be rotated on a schedule. Note the system, the environment, and whether the credential is shared or personal. An inventory that only covers passwords will miss the certificate that takes down checkout.
Walk through the tools the team actually uses rather than starting from a generic checklist. Check the billing page, the identity provider, and the infrastructure console for renewal notices. Ask each owner to confirm the systems they rely on, because a forgotten integration can hide for months. Mark anything that cannot be inventoried as an open risk rather than leaving it blank.
Record the fields that make renewal possible
For each credential, record the system, the named owner, the expiry date, the renewal method, and any downstream dependency. Add the last rotation date and the person who performed it so the history is visible. Note whether renewal requires a phone call, a support ticket, or a self-service portal. The register should let a new assistant start the renewal without reconstructing the process.
Do not store the secret, the recovery code, or the full account number in the register. Keep a pointer to the approved vault entry or the owner's documented process instead. Record the environment and the impact of an outage so the owner can prioritize. A register that becomes a secret store creates a worse risk than the expiry it was meant to prevent.
Separate monitoring from rotation authority
The assistant can monitor dates, prepare the change request, and confirm that a renewal happened. Rotating a production key, changing a domain registrar, or resetting an owner account should stay with the named owner. Write that boundary into the register so a new assistant does not infer authority from a reminder task. The distinction is especially important when a deadline creates pressure.
For low-risk credentials, the owner may delegate rotation with a written procedure and a test step. Record the delegation, the limit, and the review date rather than relying on a verbal agreement. If the procedure changes, issue a new version and retire the old one. Delegation should be specific to the credential, not a general permission to change any account.
Build the renewal calendar backwards from expiry
Set reminders at 30, 14, and 3 days before expiry, plus one after the change to confirm the new credential works. Put the reminders on a shared calendar with the owner and a backup reviewer, not only in the assistant's task list. Include the test step in the reminder so a renewal is not marked complete when the old credential still works. A deadline without a test is only a notification.
For certificates and domains, add a longer lead time because registrar and support queues can take days. Check the time zone of the expiry, since a certificate may lapse during the team's night. If the credential affects customers, schedule the change in a low-traffic window and prepare a rollback step. The calendar should show the work, not just the date.
Handle a missed expiry without hiding it
When a credential expires unexpectedly, record the time it was discovered, the systems affected, and the temporary workaround used. Notify the owner immediately and keep a short timeline as the response unfolds. Do not quietly reset the credential and move on, because the gap may have exposed data or broken an integration. The incident note should be specific enough to prevent a repeat.
After service is restored, identify whether the register missed the item, the reminder failed, or the renewal was blocked. Fix the register field or the reminder rule and test the next renewal against the fix. Add the incident to the quarterly review so the pattern is visible. A missed expiry is a process finding, not only an individual mistake.
Review the register monthly and after offboarding
Check upcoming expiries, stale owners, and entries with no renewal method at the start of each month. Remove credentials for systems that were retired, and add any new tool that appeared during the month. Confirm that every entry still has a named owner who is currently employed. An owner who left last quarter is a silent gap in the register.
After any offboarding, review every credential the person could access and rotate the ones that were shared. Record the rotation date and the new owner in the register. If a credential cannot be rotated immediately, document the compensating control and the deadline. The register should reflect the team as it is today, not as it was when it was created.
Questions and operating boundary
Should the register store passwords?
No. Store a pointer to the approved vault entry and the renewal process, never the secret itself.
Who rotates production credentials?
The named owner, unless a specific written delegation with a test step has been approved.
What belongs in a missed-expiry note?
Discovery time, affected systems, workaround, root cause, and the register fix that prevents a repeat.
Source
cisa.gov provides authoritative background and does not endorse this service.