You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* CSC-31: Maximum Validity Reduction (#48)
* Update CSBR.md for proposed validity period change
Updating to mostly match ian's original verbiage. However, given that we want at least 6 months to reflect the change after enforcmeent, setting the date to January 1st of 2026 instead of the original June 15th of 2025
* Update CSBR.md
removing previous line to avoid confusion, and updating to March
* Update docs/CSBR.md
accepting change in verbiage to be clear on certificate life for certificates issued before
Co-authored-by: Corey Bonnell <dev@cbonnell.com>
* Update docs/CSBR.md
removing an extra space
Co-authored-by: Corey Bonnell <dev@cbonnell.com>
---------
Co-authored-by: Corey Bonnell <dev@cbonnell.com>
* Update relevant dates and version
* Update Ubuntu runner version (#47)
* Set Effective Date
---------
Co-authored-by: nasantia <52333284+nasantia@users.noreply.github.com>
Co-authored-by: Corey Bonnell <dev@cbonnell.com>
Co-authored-by: Corey Bonnell <corey.bonnell@digicert.com>
| 3.10 | CSC-31 | Maximum Validity Reduction | 7 November 2025 |
65
65
### 1.2.2 Relevant Dates
66
66
67
67
|**Compliance**|**Section(s)**|**Summary Description (See Full Text for Details)**|
@@ -80,6 +80,7 @@ The following Certificate Policy Identifier is reserved for use by CAs as a requ
80
80
| 2024-06-15 | 8.4.2 | For Audit Periods starting after June 30, 2024, the Signing Service MUST undergo a conformity assessment audit for compliance with these Requirements performed in accordance with one of the schemes specified in Section 8.4.2. |
81
81
| 2025-03-15 | 3.2.10 | Prior to the use of an Incorporating Agency or Registration Agency to fulfill these verification requirements, the CA MUST publicly disclose Agency Information about the Incorporating Agency or Registration Agency. |
82
82
| 2025-04-15 | 6.2.7.2 | Effective April 15, 2025, a Timestamp Authority MUST protect Private Keys associated with its Root CA certificates and Subordinate CA certificates containing the "Time Stamping" EKU in offline Hardware Crypto Module. |
83
+
| 2026-03-01 | 6.3.2 | For Code Signing Certificates issued on or after March 1st, 2026, the validity period MUST NOT exceed 460 days. |
83
84
84
85
## 1.3 PKI participants
85
86
@@ -2029,7 +2030,7 @@ CAs SHALL ensure that the Subscriber’s Private Key is generated, stored, and u
2029
2030
2030
2031
Subscribers and Signing Services MAY sign Code at any point in the development or distribution process. Code Signatures may be verified at any time, including during download, unpacking, installation, reinstallation, or execution, or during a forensic investigation.
2031
2032
2032
-
The validity period for a Code Signing Certificate issued to a Subscriber or Signing Service MUST NOT exceed 39 months.
2033
+
For Code Signing Certificates issued before March 1st, 2026, the validity period MUST NOT exceed 39 months. For Code Signing Certificates issued on or after March 1st, 2026, the validity period MUST NOT exceed 460 days.
2033
2034
2034
2035
The Timestamp Certificate validity period MUST NOT exceed 135 months. The Timestamp Certificate Key Pair MUST meet the requirements in [Section 6.1.5](#615-key-sizes). The CA or Timestamp Authority SHALL NOT use a Private Key associated with a Timestamp Certificate more than 15 months after the `notBefore` date of a Timestamp Certificate.
0 commit comments