Skip to content

Commit 89ca8c6

Browse files
XolphinMartijnnasantiaCBonnell
authored
CSC-31: Maximum Validity Reduction (#48) (#51)
* 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>
1 parent f8b33cc commit 89ca8c6

2 files changed

Lines changed: 7 additions & 6 deletions

File tree

.github/workflows/build-draft-docs.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ jobs:
77
document:
88
- 'CSBR.md'
99
name: Build ${{ matrix.document }}
10-
runs-on: ubuntu-20.04
10+
runs-on: ubuntu-latest
1111
steps:
1212
- name: Checkout the code
1313
uses: actions/checkout@v4

docs/CSBR.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
22
title: Baseline Requirements for the Issuance and Management of Publicly-Trusted Code Signing Certificates
33

4-
subtitle: Version 3.9.0
4+
subtitle: Version 3.10.0
55

66
author:
77
- CA/Browser Forum
8-
date: August 1, 2024
8+
date: November 17, 2025
99

1010
copyright: |
11-
Copyright 2024 CA/Browser Forum
11+
Copyright 2025 CA/Browser Forum
1212
1313
This work is licensed under the Creative Commons Attribution 4.0 International license.
1414
---
@@ -61,7 +61,7 @@ The following Certificate Policy Identifier is reserved for use by CAs as a requ
6161
| 3.7 | CSC-22 | High risk changes | 28 February 2024 |
6262
| 3.8 | CSC-25 | Import EV Guidelines into the Code Signing Baseline Requirements | 1 August 2024 |
6363
| 3.9 | CSC-26 | Timestamping Private Key Protection | 1 August 2024 |
64-
64+
| 3.10 | CSC-31 | Maximum Validity Reduction | 7 November 2025 |
6565
### 1.2.2 Relevant Dates
6666

6767
| **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
8080
| 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. |
8181
| 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. |
8282
| 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. |
8384

8485
## 1.3 PKI participants
8586

@@ -2029,7 +2030,7 @@ CAs SHALL ensure that the Subscriber’s Private Key is generated, stored, and u
20292030

20302031
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.
20312032

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.
20332034

20342035
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.
20352036

0 commit comments

Comments
 (0)