Have something to say?
CertOps features
Described here https://github.com/tokentimerch/tokentimer-core/blob/main/ROADMAP.md#certops-program-certificate-lifecycle-orchestration
[Import integrations] Regex filtering
https://github.com/tokentimerch/tokentimer-core/issues/63#issuecomment-4990866704 “It would be beneficial to support importing GitLab tokens based on their name or description matching one or more user-defined regex patterns. Goal: Exclude tokens created by individual users or development teams from scanning/tracking, as their lifecycle management is the responsibility of those respective teams. This ensures the platform team retains oversight of managed tokens without receiving noise/alerts for user-created tokens.” —> this feature could also concern other integrations, but since metadata differs based on the providers, a V1 could simply to filter on the names
(core/enterprise) Auto-sync: Multiple providers per workspace
As of today, one workspace can only have one provider of a kind so a user must create another workspace to have another similar provider setup (e.g. 2 Gitlab instances)
Allow multiple admins per workspace (Cloud edition)
An admin should be able to define other admins from members of a workspace or to pass the lead to another user
Auto-renewal
Actionnable buttons to trigger API based renewal actions (cloud providers or custom)
Imported tokens : creation and last usage date
User requested to know when a token imported was created or last used, to have a better view of forgotten or old tokens
Display import date per integration
User requested to be able to see the last time an integration was synced so it’s easier to know when the inventory from a provider actually was made for the last time
Add deduplication mechanism
New token matching name + location should merge content from old token and new one after user confirmation, both in manual creation and import features.
Intelligent Alerting
Email notifications Webhooks (Slack, Discord, Teams, PagerDuty, Generic) WhatsApp notifications
Team collaboration
Basic user management Activity audit logs Role-based access control Team workspaces & sections Weekly digest summaries of expiring assets
Incident response workflows
ITSM/ticketing tools Integration : token lifecycle related task (Jira, ServiceNow, GLPI, Trello/Asana, PagerDuty, etc…) : Auto-escalation: when critical assets expire, automatically create incidents in PagerDuty/Jira/Opsgenie Runbook automation: trigger predefined workflows (e.g., rotate keys, renew certificates) when thresholds are hit Post-mortem tracking: link expired assets to incident reports, track root causes On-call routing: route critical expiration alerts to the right on-call engineer based on asset ownership Incident prevention: analyze patterns to predict and prevent incidents before they occur Integration hooks: connect to incident management tools to create tickets, update status, and auto-resolve when assets are renewed