[cabfpub] [External] Draft Working Group Charter for Network Security WG
Tony.Rutkowski at cisecurity.org
Mon Nov 1 13:59:01 UTC 2021
As the rapporteur for the new revised V8 version of the Critical Security Controls at ETSI TC CYBER as well as CIS’ representative, might I suggest that if the new working group gets underway that it consider developing a profile of the Controls what would be applicable within the scope of the new work. I have attached the latest version set for adoption in two weeks. There are multiple considerable advantages to using the Controls that includes extensive global adoption and use by multiple communities and nations, cross mapping to almost all other control schemes, inclusion into an array of automation tools, and instantiation into all cloud OS platforms. It also has a very active user/developer community. See CIS Critical Security Controls (cisecurity.org)<https://www.cisecurity.org/controls/>
From: Public <public-bounces at cabforum.org> On Behalf Of Ben Wilson via Public
Sent: Thursday, 28 October, 2021 12:35 PM
To: CA/Browser Forum Public Discussion List <public at cabforum.org>
Subject: [External] [cabfpub] Draft Working Group Charter for Network Security WG
Here is a draft charter for a Network Security Working Group. Please provide your comments, and then we will finalize this work in the form of a Forum Ballot and Server Certificate WG Ballot.
In January 2013 the CA/Browser Forum’s “Network and Certificate System Security Requirements” (NCSSRs) became effective. In June 2017, the Forum chartered a Network Security Working Group to re-visit the NCSSRs. That charter expired on June 19, 2018, and in October 2018, the Server Certificate Working Group (SCWG) established a Network Security Subcommittee (NetSec Subcommittee) to continue work on the NCSSRs.
This ballot proposes to charter a new Network Security Working Group (NetSec WG) to replace the NetSec Subcommittee, to continue work on the NCSSRs, and to conduct any and all business related to improving the security of Certification Authorities.
Following the passage of this/these ballot(s):
1. A new NetSec WG will be chartered under the CA/B Forum, pursuant to section 5.3.1 of the Bylaws;
2. The SCWG’s existing NetSec Subcommittee will be dissolved by the SCWG and the Charter of the SCWG will be amended to note that work on the NCSSRs are within the authorized scope of the NetSec WG;
3. The existing mailing list and other materials developed for the NetSec Subcommittee will be repurposed for use by the NetSec WG; and
4. The Forum will develop a procedure to coordinate the NetSec WG’s adoption of security-related recommendations for requirements or guidelines that are within the purview of the other Forum WGs (the BRs/EVGs by the SCWG, Baseline Requirements for Code Signing Certificates of the CSCWG, etc.).
NetSec WG Charter
A chartered Working Group (“NetSec WG”) is created to perform the activities as specified in this Charter, subject to the terms and conditions of the CA/Browser Forum Bylaws (https://cabforum.org/bylaws/<https://cabforum.org/bylaws/>) and Intellectual Property Rights (IPR) Policy (https://cabforum.org/ipr-policy/<https://cabforum.org/ipr-policy>), as such documents may change from time to time. This charter for the NetSec WG has been created according to CAB Forum Bylaw 5.3.1. In the event of a conflict between this Charter and any provision in either the Bylaws or the IPR Policy, the provision in the Bylaws or IPR Policy shall take precedence. The definitions found in the Forum’s Bylaws shall apply to capitalized terms in this Charter.
1. Scope - The scope of work performed by the NetSec WG includes:
1. To modify and maintain the existing Network and Certificate System Security Requirements (NCSSRs), or a successor requirements document;
2. To make recommendations for improvements to security controls in the requirements or guidelines adopted by other Forum WGs (e.g. see sections 5 and 6 of the Baseline Requirements);
3. To create new requirements, guidelines, and best practices related to the security of CA operations;
4. To perform risk analyses, security analyses, and other types of reviews of threats and vulnerabilities applicable to CA operations involved in the issuance and maintenance of publicly trusted certificates (e.g. server certificates, code signing certificates, SMIME certificates, etc.); and
5. To perform other activities ancillary to the primary activities listed above.
2. Out of Scope – The NetSec WG shall not adopt requirements, Guidelines, or Maintenance Guidelines concerning certificate profiles, validation processes, certificate issuance, certificate revocation, or subscriber obligations.
3. End Date – The NetSec WG shall continue until it is dissolved by a vote of the CA/B Forum.
4. Deliverables - The NetSec WG shall be responsible for delivering and maintaining the NCSSRs and any other documents the group may choose to develop and maintain.
5. Participation and Membership – Membership in the NetSec WG shall be limited to Certificate Issuer Members and Certificate Consumer Members of the Server Certificate Working Group, the Code Signing Certificate Working Group, or the SMIME Certificate Working Group.
In accordance with the IPR Policy, Members that choose to participate in the NetSec WG MUST declare their participation and shall do so prior to participating. A Member must declare its participation in the NetSec WG by requesting to be added to the mailing list. The Chair of the NetSec WG shall establish a list for declarations of participation and manage it in accordance with the Bylaws, the IPR Policy, and the IPR Agreement.
The NetSec WG shall include Interested Parties and Associate Members as defined in the Bylaws.
Resignation from the NetSec WG does not prevent a participant from potentially having continuing obligations under the Forum’s IPR Policy or any other document.
6. Voting Structure
The NetSec WG shall consist of two classes of voting members, Certificate Issuers and Certificate Consumers. In order for a ballot to be adopted by the NetSec WG, two-thirds or more of the votes cast by the Certificate Issuers must be in favor of the ballot and more than 50% of the votes cast by the Certificate Consumers must be in favor of the ballot. At least one member of each class must vote in favor of a ballot for it to be adopted. Quorum is the average number of Member organizations (cumulative, regardless of Class) that have participated in the previous three NetSec WG Meetings or Teleconferences (not counting subcommittee meetings thereof). For transition purposes, if three meetings have not yet occurred, then quorum is ten (10).
Chair – Clint Wilson shall be the initial Chair of the NetSec WG.
Vice-Chair - David Kluge shall be the initial Vice-Chair of the NetSec WG.
Term. The Chair and Vice-Chair will serve until October 31, 2022, or until they are replaced, resign, or are otherwise disqualified. Thereafter, elections shall be held for chair and vice chair every two years in coordination with the Forum’s election process and in conjunction with its election cycle. Voting shall occur in accordance with Bylaw 4.1(c). In the event of a midterm vacancy, the NetSec WG will hold a special election and the selected candidate will serve the remainder of the existing term.
8. Communication - NetSec WG communications and documents shall be posted on mailing-lists where the mail-archives are publicly accessible, and the NetSec WG shall publish minutes of its meetings to the Forum’s website.
9. IPR Policy - The CA/Browser Forum Intellectual Rights Policy, v. 1.3 or later, shall apply to all Working Group activity.
10. Other Organizational Matters
Effect of Forum Bylaws Amendment on Working Group - In the event that Forum Bylaws are amended to add or modify general rules governing Forum Working Groups and how they operate, such provisions of the Bylaws take precedence over this charter.
This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments.
. . . . .
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1908449 bytes
More information about the Public