Knowledge Base

Usage and Subscriptions in Sectigo Certificate Manager (SCM) 

Overview: 

This article provides a combined explanation of Usage and Subscriptions in Sectigo Certificate Manager (SCM), including real UI screenshots for clarity. Administrators can use this guide to understand how certificate consumption is tracked, how entitlements are structured, and how to interpret the SCM dashboard. 

1. Understanding Usage 

Usage in SCM refers to how certificate inventories and entitlements are consumed across SSL, client, device, and codesigning categories. This information helps administrators track issuance volume, identify overages, and ensure subscription limits are respected. 

Usage includes: 

• Issued certificates 

• Remaining inventory 

• Overages 

• Allocation across certificate types 

• Department or organization consumption 

Monitoring usage is essential for capacity planning, budgeting, and subscription management. 

1.1 Usage Page Screenshot 

The screenshot below reflects the Usage dashboard, showing inventory, consumed counts, availability, and overage indicators. 

SCM Usage Interface Example 

1.2 How to Interpret the Usage Dashboard 

SSL Certificates 

The SSL section shows DV, OV, and other certificate categories. 
For each category, administrators can see: 

• Usage (number of certificates issued) 

• Inventory (total available certificates) 

• Available (unused certificates) 

• Overage (red warning icons if usage exceeds inventory) 

Client Certificates 

Displays allocations for S/MIME and authentication certificates. 
Overages appear when consumption exceeds allocated inventory. 

Code Signing Certificates 

Shows OV and EV codesigning entitlements and remaining inventory. 

Why Usage Tracking Matters 

• Prevents issuance interruptions 

• Ensures compliance with subscription limits 

• Supports operational forecasting for certificate teams 

• Helps allocate consumption to the correct departments 

• Simplifies internal chargeback or budgeting processes 

2. Understanding Subscriptions 

Subscriptions in SCM define entitlement packages, contract periods, certificate limits, and organizational access. They determine what certificate types and quantities an organization can use and how consumption is billed. 

Subscriptions typically include: 

• SSL bundles 

• S/MIME or Client Certificate allocations 

• Device certificate entitlements 

• Private CA issuance 

• Enterprise agreements 

• Addon inventory packages 

2.1 Subscriptions Page Screenshot 

The screenshot below presents the Subscriptions interface, showing subscription identifiers, created dates, and contract periods. 

SCM Subscriptions Interface Example 

2.2 How to Interpret the Subscriptions Dashboard 

Subscription Identifier 

Each subscription row contains a unique encoded ID representing the entitlement package. 

Created Date 

Indicates when the subscription record was added into SCM. 

Start and End Dates 

Define the active contract window. Certificate issuance is only counted against inventory within this date range. 

Multiple Subscriptions 

Organizations may have multiple subscriptions active at once, such as: 

• A general SSL license 

• A device certificate license 

• An S/MIME entitlement package 

Purchase / Renewal 

The Purchase button allows admins to request additional entitlements or initiate subscription upgrades. 

3. Relationship Between Usage and Subscriptions 

Usage and subscriptions work together: 

• Subscriptions define what you can use. 

• Usage shows what you have used. 

Understanding both is necessary for: 

• Preventing outages due to zero remaining inventory 

• Managing budgets 

• Avoiding overage charges 

• Ensuring certificate availability across all departments 

• Sizing future subscription renewals 

• Supporting security programs requiring high-volume certificate issuance (e.g., DevOps, MDM, ZeroTrust) 

4. Best Practices for Administrators 

• Review both Usage and Subscriptions monthly. 

• Ensure subscriptions are renewed before expiration to prevent issuance blocking. 

• Use historical usage trends to plan for subscription upgrades. 

• Assign organizational password or certificate policies to control who consumes inventory. 

• Monitor overage indicators proactively. 

• Keep departments aligned with subscription boundaries. 

• Request expanded entitlements when upcoming projects will increase issuance demand. 

Related Articles:  

Tags: