Re: [cabfpub] [EXTERNAL] FW: Ballot FORUM-10: Re-charter Forum Infrastructure Working Group

[Ben Wilson via Public]

DigiCert votes YES on Ballot FORUM-10.

 

From: Public mailto:public-boun...@cabforum.org> 
> On Behalf Of Jos Purvis (jopurvis) via Public
Sent: Monday, September 30, 2019 11:27 AM
To: CA/B Forum Public List mailto:public@cabforum.org> >
Subject: [EXTERNAL][cabfpub] FW: Ballot FORUM-10: Re-charter Forum 
Infrastructure Working Group

 

The following ballot is proposed by Jos Purvis of Cisco, endorsed by Wayne 
Thayer of Mozilla and Ben Wilson of DigiCert. Voting begins at 2100 UTC 30 
September 2019 and runs through 2100 UTC 7 October 2019.

 

Ballot Forum-10: Re-charter Forum Infrastructure Work

Overview

The Forum Infrastructure Working Group (FIWG) was chartered during a period 
when the CABF Bylaws did not permit for the creation of subcommittees at the 
Forum level (only under a particular Working Group). Since the work the FIWG 
needed to undertake was pressing and covered the needs of the Forum as a whole, 
it was chartered as a Working Group to permit this work to begin under the 
existing Bylaws.

With the completion of the recent Bylaws changes, subcommittees may now be 
constructed at the Forum level. In addition, the recent changes to Bylaws and 
membership have identified a hole by which membership in the FIWG could be used 
to “back-door” membership in the Forum as a whole, an unintended consequence 
worth squashing.

This ballot, therefore, lays down the existing FIWG and immediately re-charters 
a Forum Infrastructure Subcommittee to continue its work.

 

Gory Details

24 hours after this ballot passes the following will occur:

1.   The existing Forum Infrastructure Working Group will be dissolved per 
the Bylaws section 5.3.2 item 3.

2.  A new Infrastructure Subcommittee will be chartered under the CA/B 
Forum, per the Bylaws section 5.6, with the Charter of that Subcommittee as 
described below.

3.  The existing mailing list for the FIWG will be repurposed for the use 
of the Subcommittee, following an announcement to that end on the existing FIWG 
mailer.

4.  The existing wiki pages from the FIWG will be archived, and a new space 
created for the Subcommittee's use under the main Forum namespace.

 

Forum Infrastructure Subcommittee (FIS) Charter

Scope - The authorized scope of the Forum Infrastructure Subcommittee shall be 
as follows:

· To oversee the acquisition, operation, and maintenance of the common 
CA/Browser Forum website and wiki resources;

· To coordinate updates to public and Forum-facing web and wiki content 
in support of the Forum Webmaster role established in the Bylaws;

· To create and manage the division of access and content spaces 
required to help ensure the separation of the work of various Working Groups 
and accompanying IP commitments, as described in the Forum’s IPR Policy;

· To manage the technical means of production of guidelines and other 
documents produced by the Forum's subcommittees;

· To manage the Forum-level email lists and to offer management of 
working-group and subcommittee mailing lists as needed in support of the Forum 
List Manager role established in the Bylaws;

· To perform other activities ancillary to the primary activities 
listed above.

End Date - This Subcommittee shall continue until it is dissolved by a vote of 
the CA/B Forum.

Deliverables - The Forum Infrastructure Subcommittee shall be responsible for 
delivering wiki and mailing list services to the Forum on an ongoing basis, and 
supplying access to these and to the management tools for these as is 
appropriate and required by the Forum. The subcommittee shall not propose any 
changes to the Bylaws or IPR agreements itself: where issues with these are 
identified, they may be redirected to the Forum as a whole or to appropriate 
subcommittees or working groups for further consideration.

Participation - Any member of the CAB Forum is eligible and may declare their 
participation in the Forum Infrastructure Subcommittee by requesting to be 
added to the mailing list. 

Chair - Jos Purvis shall be the initial Chair of the Forum Infrastructure 
Subcommittee. The Chair shall not have a fixed term, but the Subcommittee may 
change its Chair from time to time by consensus of the Members participating in 
the Subcommittee or by voting method chosen by the Members by consensus.

Communication - Subcommittee communications and documents shall be posted on 
mailing-lists where the mail-archives are publicly accessible, and the 
Subcommittee shall publish minutes of its meetings to the Forum wiki.

Effect of Forum Bylaws Amendment for Subcommittees - In the event the Forum 
Bylaws are amended to add or modify general rules governing Forum Subcommittees 
and how they operate (“General Rules”), the provisions of the General Rules 
shall take precedence over this charter.

 

Key Dates


Ballot Discussion Begins

20 Sept 2019 21:00 UTC


Ballot Discussion Concludes

27 Sept 2019 21:00 UTC


Ballot Vote Begins

Re: [cabfpub] [FEEDBACK NEEDED] Pull Request: Pandoc-Friendly Formatting

[Jos Purvis (jopurvis) via Public]

In case anyone is interested in seeing how the BR document renders in GitHub 
with these changes, I’ll save you clicking around to find it:

    
https://github.com/cabforum/documents/blob/1fd64fdb7bdc84c83c98c584db602ae77965c749/docs/BR.md

 

😊

 

 

-- 
Jos Purvis (jopur...@cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)

 

From: Public  on behalf of CA/B Forum Public List 

Reply-To: "Jos Purvis (jopurvis)" , CA/B Forum Public List 

Date: Thursday, October 3, 2019 at 11:42 AM
To: CA/B Forum Public List 
Subject: [cabfpub] [FEEDBACK NEEDED] Pull Request: Pandoc-Friendly Formatting

 

All,

 

I’ve created a pull request containing the formatting changes necessary to 
permit using pandoc to automatically convert the BRs from Markdown to PDF, 
HTML, and Word/DOCX. I think the changes are whitespace and markup 
modifications that do not change the content or meaning of the BRs, but since 
it’s a significant number of changes, I’m happy to bring it to ballot (or 
incorporate it into the next ‘Cleanup Ballot’) if people would prefer.

 

The link to the pull request is below; I’d welcome feedback on whether and how 
people would like this brought to ballot.

 

https://github.com/cabforum/documents/pull/142

 

Cheers,

 

Jos

 

-- 
Jos Purvis (jopur...@cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)



smime.p7s
Description: S/MIME cryptographic signature
___
Public mailing list
Public@cabforum.org
https://cabforum.org/mailman/listinfo/public

[cabfpub] [FEEDBACK NEEDED] Pull Request: Pandoc-Friendly Formatting

[Jos Purvis (jopurvis) via Public]

All,

 

I’ve created a pull request containing the formatting changes necessary to 
permit using pandoc to automatically convert the BRs from Markdown to PDF, 
HTML, and Word/DOCX. I think the changes are whitespace and markup 
modifications that do not change the content or meaning of the BRs, but since 
it’s a significant number of changes, I’m happy to bring it to ballot (or 
incorporate it into the next ‘Cleanup Ballot’) if people would prefer.

 

The link to the pull request is below; I’d welcome feedback on whether and how 
people would like this brought to ballot.

 

https://github.com/cabforum/documents/pull/142

 

Cheers,

 

Jos

 

-- 
Jos Purvis (jopur...@cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)



smime.p7s
Description: S/MIME cryptographic signature
___
Public mailing list
Public@cabforum.org
https://cabforum.org/mailman/listinfo/public

Re: [cabfpub] FW: Ballot FORUM-10: Re-charter Forum Infrastructure Working Group

[Wojciech Trapczyński via Public]

Certum votes Yes to ballot FORUM-10.

-Wojciech Trapczyński

On 30.09.2019 17:27, Jos Purvis (jopurvis) via Public wrote:
The following ballot is proposed by Jos Purvis of Cisco, endorsed by 
Wayne Thayer of Mozilla and Ben Wilson of DigiCert. Voting begins at 
*2100 UTC 30 September 2019* and runs through *2100 UTC 7 October 2019*.


*/Ballot Forum-10: Re-charter Forum Infrastructure Work/*

*Overview*

The Forum Infrastructure Working Group (FIWG) was chartered during a 
period when the CABF Bylaws did not permit for the creation of 
subcommittees at the Forum level (only under a particular Working 
Group). Since the work the FIWG needed to undertake was pressing and 
covered the needs of the Forum as a whole, it was chartered as a Working 
Group to permit this work to begin under the existing Bylaws.


With the completion of the recent Bylaws changes, subcommittees may now 
be constructed at the Forum level. In addition, the recent changes to 
Bylaws and membership have identified a hole by which membership in the 
FIWG could be used to “back-door” membership in the Forum as a whole, an 
unintended consequence worth squashing.


This ballot, therefore, lays down the existing FIWG and immediately 
re-charters a Forum Infrastructure Subcommittee to continue its work.


**

*Gory Details*

24 hours after this ballot passes the following will occur:

1.The existing Forum Infrastructure Working Group will be dissolved per 
the Bylaws section 5.3.2 item 3.


2.A new Infrastructure Subcommittee will be chartered under the CA/B 
Forum, per the Bylaws section 5.6, with the Charter of that Subcommittee 
as described below.


3.The existing mailing list for the FIWG will be repurposed for the use 
of the Subcommittee, following an announcement to that end on the 
existing FIWG mailer.


4.The existing wiki pages from the FIWG will be archived, and a new 
space created for the Subcommittee's use under the main Forum namespace.


**

*Forum Infrastructure Subcommittee (FIS) Charter*

*Scope* - The authorized scope of the Forum Infrastructure Subcommittee 
shall be as follows:


·To oversee the acquisition, operation, and maintenance of the common 
CA/Browser Forum website and wiki resources;


·To coordinate updates to public and Forum-facing web and wiki content 
in support of the Forum Webmaster role established in the Bylaws;


·To create and manage the division of access and content spaces required 
to help ensure the separation of the work of various Working Groups and 
accompanying IP commitments, as described in the Forum’s IPR Policy;


·To manage the technical means of production of guidelines and other 
documents produced by the Forum's subcommittees;


·To manage the Forum-level email lists and to offer management of 
working-group and subcommittee mailing lists as needed in support of the 
Forum List Manager role established in the Bylaws;


·To perform other activities ancillary to the primary activities listed 
above.


*End Date* - This Subcommittee shall continue until it is dissolved by a 
vote of the CA/B Forum.


*Deliverables* - The Forum Infrastructure Subcommittee shall be 
responsible for delivering wiki and mailing list services to the Forum 
on an ongoing basis, and supplying access to these and to the management 
tools for these as is appropriate and required by the Forum. The 
subcommittee shall not propose any changes to the Bylaws or IPR 
agreements itself: where issues with these are identified, they may be 
redirected to the Forum as a whole or to appropriate subcommittees or 
working groups for further consideration.


*Participation* - Any member of the CAB Forum is eligible and may 
declare their participation in the Forum Infrastructure Subcommittee by 
requesting to be added to the mailing list.


*Chair* - Jos Purvis shall be the initial Chair of the Forum 
Infrastructure Subcommittee. The Chair shall not have a fixed term, but 
the Subcommittee may change its Chair from time to time by consensus of 
the Members participating in the Subcommittee or by voting method chosen 
by the Members by consensus.


*Communication* - Subcommittee communications and documents shall be 
posted on mailing-lists where the mail-archives are publicly accessible, 
and the Subcommittee shall publish minutes of its meetings to the Forum 
wiki.


*Effect of Forum Bylaws Amendment for Subcommittees* - In the event the 
Forum Bylaws are amended to add or modify general rules governing Forum 
Subcommittees and how they operate (“General Rules”), the provisions of 
the General Rules shall take precedence over this charter.


*Key Dates*

/Ballot Discussion Begins/



20 Sept 2019 21:00 UTC

/Ballot Discussion Concludes/



27 Sept 2019 21:00 UTC

/Ballot Vote Begins/



30 Sept 2019 21:00 UTC

/Ballot Vote Ends/



7 Oct 2019 21:00 UTC

--
Jos Purvis (jopur...@cisco.com )
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  |

Re: [cabfpub] Ballot FORUM-10: Re-charter Forum Infrastructure Working Group

[Neil Dunbar via Public]

TrustCor votes YES on Ballot FORUM-10

Regards,

Neil

> On 30 Sep 2019, at 16:27, Jos Purvis (jopurvis) via Public 
>  wrote:
> 
> The following ballot is proposed by Jos Purvis of Cisco, endorsed by Wayne 
> Thayer of Mozilla and Ben Wilson of DigiCert. Voting begins at 2100 UTC 30 
> September 2019 and runs through 2100 UTC 7 October 2019.
>  
> Ballot Forum-10: Re-charter Forum Infrastructure Work
> Overview
> The Forum Infrastructure Working Group (FIWG) was chartered during a period 
> when the CABF Bylaws did not permit for the creation of subcommittees at the 
> Forum level (only under a particular Working Group). Since the work the FIWG 
> needed to undertake was pressing and covered the needs of the Forum as a 
> whole, it was chartered as a Working Group to permit this work to begin under 
> the existing Bylaws.
> With the completion of the recent Bylaws changes, subcommittees may now be 
> constructed at the Forum level. In addition, the recent changes to Bylaws and 
> membership have identified a hole by which membership in the FIWG could be 
> used to “back-door” membership in the Forum as a whole, an unintended 
> consequence worth squashing.
> This ballot, therefore, lays down the existing FIWG and immediately 
> re-charters a Forum Infrastructure Subcommittee to continue its work.
>  
> Gory Details
> 24 hours after this ballot passes the following will occur:
> 1.   The existing Forum Infrastructure Working Group will be dissolved 
> per the Bylaws section 5.3.2 item 3.
> 2.  A new Infrastructure Subcommittee will be chartered under the CA/B 
> Forum, per the Bylaws section 5.6, with the Charter of that Subcommittee as 
> described below.
> 3.  The existing mailing list for the FIWG will be repurposed for the use 
> of the Subcommittee, following an announcement to that end on the existing 
> FIWG mailer.
> 4.  The existing wiki pages from the FIWG will be archived, and a new 
> space created for the Subcommittee's use under the main Forum namespace.
>  
> Forum Infrastructure Subcommittee (FIS) Charter
> Scope - The authorized scope of the Forum Infrastructure Subcommittee shall 
> be as follows:
> · To oversee the acquisition, operation, and maintenance of the 
> common CA/Browser Forum website and wiki resources;
> · To coordinate updates to public and Forum-facing web and wiki 
> content in support of the Forum Webmaster role established in the Bylaws;
> · To create and manage the division of access and content spaces 
> required to help ensure the separation of the work of various Working Groups 
> and accompanying IP commitments, as described in the Forum’s IPR Policy;
> · To manage the technical means of production of guidelines and other 
> documents produced by the Forum's subcommittees;
> · To manage the Forum-level email lists and to offer management of 
> working-group and subcommittee mailing lists as needed in support of the 
> Forum List Manager role established in the Bylaws;
> · To perform other activities ancillary to the primary activities 
> listed above.
> End Date - This Subcommittee shall continue until it is dissolved by a vote 
> of the CA/B Forum.
> Deliverables - The Forum Infrastructure Subcommittee shall be responsible for 
> delivering wiki and mailing list services to the Forum on an ongoing basis, 
> and supplying access to these and to the management tools for these as is 
> appropriate and required by the Forum. The subcommittee shall not propose any 
> changes to the Bylaws or IPR agreements itself: where issues with these are 
> identified, they may be redirected to the Forum as a whole or to appropriate 
> subcommittees or working groups for further consideration.
> Participation - Any member of the CAB Forum is eligible and may declare their 
> participation in the Forum Infrastructure Subcommittee by requesting to be 
> added to the mailing list. 
> Chair - Jos Purvis shall be the initial Chair of the Forum Infrastructure 
> Subcommittee. The Chair shall not have a fixed term, but the Subcommittee may 
> change its Chair from time to time by consensus of the Members participating 
> in the Subcommittee or by voting method chosen by the Members by consensus.
> Communication - Subcommittee communications and documents shall be posted on 
> mailing-lists where the mail-archives are publicly accessible, and the 
> Subcommittee shall publish minutes of its meetings to the Forum wiki.
> Effect of Forum Bylaws Amendment for Subcommittees - In the event the Forum 
> Bylaws are amended to add or modify general rules governing Forum 
> Subcommittees and how they operate (“General Rules”), the provisions of the 
> General Rules shall take precedence over this charter.
>  
> Key Dates
> Ballot Discussion Begins
> 20 Sept 2019 21:00 UTC
> Ballot Discussion Concludes
> 27 Sept 2019 21:00 UTC
> Ballot Vote Begins
> 30 Sept 2019 21:00 UTC
> Ballot Vote Ends
> 7 Oct 2019 21:00 UTC
>  
>  
>  
> -- 
> Jos

[cabfpub] Specification group on Securing Artificial Intelligence

[Arno Fiedler via Public]

Hello,
I think thats relevant in context of Code-Signing Use Cases
Best regards
Arno

ETSI announce the creation of a new Industry Specification Group on 
Securing Artificial Intelligence (ISG SAI). The group will develop 
technical specifications to mitigate threats arising from the deployment 
of AI throughout multiple ICT-related industries. This includes threats 
to artificial intelligence systems from both conventional sources and 
other AIs.


The ETSI Securing Artificial Intelligence group was initiated to 
anticipate that autonomous mechanical and computing entities may make 
decisions that act against the relying parties either by design or as a 
result of malicious intent. The conventional cycle of networks risk 
analysis and countermeasure deployment represented by the 
Identify-Protect-Detect-Respond cycle needs to be re-assessed when an 
autonomous machine is involved.


The intent of the ISG SAI is therefore to address 3 aspects of 
artificial intelligence in the standards domain:


 *      Securing AI from attack e.g. where AI is a component in the
   system that needs defending
 *      Mitigating against AI e.g. where AI is the ‘problem’ or is used
   to improve and enhance other more conventional attack vectors
 *      Using AI to enhance security measures against attack from other
   things e.g. AI is part of the ‘solution’ or is used to improve and
   enhance more conventional countermeasures.

The purpose of the ETSI ISG SAI is to develop the technical knowledge 
that acts as a baseline in ensuring that artificial intelligence is 
secure. Stakeholders impacted by the activity of ETSI’s group include 
end users, manufacturers, operators and governments.


Three main activities will be undertaken and confirmed during the first 
meeting of the group.
*AI Threat Ontology *Currently, there is no common understanding of what 
constitutes an attack on AI and how it might be created, hosted and 
propagated. The work to be undertaken here will seek to define what 
would be considered an AI threat and how it might differ from threats to 
traditional systems.


Hence, the AI Threat Ontology specification seeks to align terminology 
across the different stakeholders and multiple industries. ETSI 
specifications will define what is meant by these terms in the context 
of cyber and physical security and with a narrative that should be 
readily accessible to all. This threat ontology will address AI as 
system, attacker and defence.
*Securing AI Problem Statement *This specification will be modelled on 
the ETSI GS NFV-SEC 001 “Security Problem Statement” which has been 
highly influential in guiding the scope of ETSI NFV and enabling 
“security by design” for NFV infrastructures. It will define and 
prioritize potential AI threats along with recommended actions. The 
recommendations contained in this specification will be used to define 
the scope and timescales for the follow-up work.
*Data Supply Chain Report *Data is a critical component in the 
development of AI systems, both raw data, and information and feedback 
from other AI systems and humans in the loop. However, access to 
suitable data is often limited, causing a need to resort to less 
suitable sources of data. Compromising the integrity of data has been 
demonstrated to be a viable attack vector against an AI system.


This report will summarize the methods currently used to source data for 
training AI, along with a review of existing initiatives for developing 
data sharing protocols and analyse requirements for standards for 
ensuring integrity in the shared data, information and feedback, as well 
as the confidentiality of these.
The founding members of the new ETSI group include BT, Cadzow 
Communications, Huawei Technologies, NCSC and Telefónica.
The first meeting of ISG SAI will be held in Sophia Antipolis on 23 
October. Come and join to shape the future path for secure artificial 
intelligence!


*Contact
*Claire Boyer
Mob: +33 (0)6 87 60 84 40

Email: claire.bo...@etsi.org 



 Weitergeleitete Nachricht 
Betreff: 	[ISG_SAI] Press release: ETSI launches specification group on 
Securing Artificial Intelligence

Datum:  Wed, 2 Oct 2019 08:47:01 +
Von:Sonia Compans 
Antwort an: 	ISG_SAI Securing Artificial Intelligence 


An: isg_...@list.etsi.org



Dear SAI,

We launched the press release announcing the ISG creation.

Do not hesitate to forward

https://www.etsi.org/newsroom/press-releases/1650-2019-10-etsi-launches-specification-group-on-securing-artificial-intelligence

Sonia

*Sonia Compans–*Technical Officer

*ETSI*● www.etsi.org  ●_sonia.comp...@etsi.org 
_


Phone: +33 (0)4 92 94 43 36 ●Mobile: +33 (0)6 67 15 58 49

Watch the new ETSI video _Cybersecurity: join the players 
_


** **

This email may contain confidential information and is intended fo