1.0 Introduction
Fortanix Confidential Computing Manager (CCM) allows administrators to configure a security patching grace period for their account. This setting specifies the number of days registered nodes have to apply required security patches after a hardware vendor publicly discloses a vulnerability affecting confidential computing. Fortanix CCM uses this setting to evaluate registered nodes. Fortanix CCM applies the configured grace period to all supported platforms in the account.
Until you change this setting, Fortanix CCM applies the default grace period of 42 days (6 weeks). You can configure a value from 0 to 365 days.
Fortanix CCM always evaluates each node against the vendor’s latest Trusted Computing Base (TCB). The grace period decides how long a node that is behind may keep running before CCM treats it as overdue.
With the grace period, you can:
See every node’s patch status, the deadline it must meet, and the days remaining.
Patch on a predictable schedule after Intel or AMD publishes a TCB Recovery, without attestation failing on disclosure day.
Choose what happens to an overdue node, flag it, and keep it running, or block attestation and withhold Secure Key Release.
NOTE
When multiple patches are released, each new TCB level has its own grace period, based on the grace period configured at the account level. If you extend the grace period before it expires, the updated policy applies to all supported platforms. This can prevent attestation failures for TCB levels that are still within the extended grace period.
2.0 Key Concepts
TERM | MEANING IN CCM |
|---|---|
Trusted Computing Base (TCB) | The hardware, firmware, and software that a Trusted Execution Environment’s (TEE) security depends on, such as CPU microcode, the TDX module, and SEV-SNP firmware. |
TCB Recovery | A vendor event that discloses a vulnerability, publishes a new TCB level, and marks older levels as out of date. |
Disclosure Date | The date the vendor publicly disclosed the vulnerability. Fortanix CCM determines it for each node from the vendor’s attestation collateral. The grace period starts on this date. |
Grace Period | The number of days a node has after the disclosure date to be patched. Range: 0 to 365 days. Default: 42 days. |
Compliance Deadline | The disclosure date plus the grace period. |
Enforcement Mode | What Fortanix CCM does with an overdue node. In Block mode, Fortanix CCM denies attestation and withholds Secure Key Release. |
3.0 How Fortanix CCM Evaluates Node Patch Compliance
Every time a node attests, Fortanix CCM verifies its evidence against the vendor’s latest attestation collateral and works out the node’s status. If the node’s TCB is behind, Fortanix CCM finds the disclosure date of the vulnerability that made it out of date. It then adds your grace period to that date to get the node’s deadline.
.png?sv=2026-02-06&spr=https&st=2026-11-17T03%3A06%3A48Z&se=2026-11-17T03%3A19%3A48Z&sr=b&sp=r&sig=G13OppDJDJ0rKsbzKoVtW306Ds9xkQSZH1ZMvdOb7t4%3D)
Figure 1: Node Status and Enforcement Outcome by Mode
4.0 Supported Platforms
You configure a single grace period on the Security Policy page. This setting applies to the platforms listed in the table below.
PLATFORM | VENDOR COLLATERAL CCM EVALUATES | ALLOWED RANGE |
|---|---|---|
AMD SEV-SNP | AMD Key Distribution Service (KDS) | 0 to 365 days |
INTEL TDX + SGX | Intel Provisioning Certification Service (PCS) | 0 to 365 days |
5.0 Configure the Security Patching Grace Period
Perform the following steps to configure the Security patching grace period feature:
In the CCM UI left navigation panel, click Settings→Security Policy.
On the Security Policy for Infrastructure page, set the Security patching grace period.
Enter a whole number between 0 and 365.
NOTE
Increasing the grace period extends the time allowed to patch affected nodes and may increase their exposure to known vulnerabilities. Ensure to review the security implications before confirming the change.
.png?sv=2026-02-06&spr=https&st=2026-11-17T03%3A06%3A48Z&se=2026-11-17T03%3A19%3A48Z&sr=b&sp=r&sig=bRuKTqsjItdrQjXnY64gZPpHLeX6e%2FX2uDY%2FsbZykDE%3D)
Figure 2: Security Policy for Infrastructure
Click SAVE CHANGES.
On the Confirm security patching grace period update dialog box, re-enter the number of days entered in Step 3, and then click CONFIRM to confirm the changes.
Fortanix CCM applies the saved value to evaluations performed after the change is saved.
5.1 Reset the Security Policy to the Default Value
The Security Policy page provides a RESET TO DEFAULT option.
Perform the following steps to reset the security policy:
Navigate to Settings → Security Policy → Security Policy for Infrastructure.
Click RESET TO DEAFULT.
Verify that the Security patching grace period is set to 42 days.
If required, click SAVE CHANGES to apply the default value.