[cabfpub] Code Signing Baseline Requirements - Public Draft

i-barreira at izenpe.net i-barreira at izenpe.net
Fri Sep 5 09:04:47 UTC 2014

Now to the public list. I don´t like the word "obligated". Isn´t there any other way to say it without mandating? As said there are laws that are over the CABF requirements that are obligated to follow, not a requirements from the CABF.



Iñigo Barreira
Responsable del Área técnica
i-barreira at izenpe.net




ERNE! Baliteke mezu honen zatiren bat edo mezu osoa legez babestuta egotea. Mezua badu bere hartzailea. Okerreko helbidera heldu bada (helbidea gaizki idatzi, transmisioak huts egin) eman abisu igorleari, korreo honi erantzuna. KONTUZ!
ATENCION! Este mensaje contiene informacion privilegiada o confidencial a la que solo tiene derecho a acceder el destinatario. Si usted lo recibe por error le agradeceriamos que no hiciera uso de la informacion y que se pusiese en contacto con el remitente.


De: public-bounces at cabforum.org [mailto:public-bounces at cabforum.org] En nombre de Jeremy Rowley
Enviado el: lunes, 25 de agosto de 2014 22:29
Para: 'public at cabforum.org'
Asunto: [cabfpub] Code Signing Baseline Requirements - Public Draft


Hi everyone, 


In 2013, the CA/Browser Forum voted to create a Code Signing Working Group whose sole purpose was to come up with a set of Baseline Requirements for the issuance of Code Signing Certificates. The result of that effort is enclosed. Once approved by the CA/B Forum and subsequent audit standards are created, all Certificate Authorities will be obligated to follow these Requirements when issuing and managing code signing certificates. 


The goals of this project and resulting document are as follows:

1.       Create uniform identification and vetting procedures that all Certificate Authorities must follow when issuing code signing certificates

2.       Identify ways to stop the theft of private keys and prevent key compromise by increasing the required levels of key protection

3.       Identify origins of malware (geographic and otherwise) and implement procedures to reduce the incidence of signed malware

4.       Document standards for code signing "services" which store private code-signing keys in cloud-based service offerings


Although it may seem that the biggest beneficiaries of these guidelines will be large operating system vendors that utilize code signing certificates, the public as a whole will benefit from a reduced incidence of malware on their systems and devices. We urge users, the software development industry, and operating system platforms to carefully review this document and provide comments to the CA/B Forum by October 30, 2014. The Working Group will review every comment for incorporation into the final draft.  Comments should be sent to questions at cabforum.org <mailto:questions at cabforum.org> .

The Code Signing Working Group


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20140905/3ba04b3a/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 19121 bytes
Desc: image001.png
URL: <http://lists.cabforum.org/pipermail/public/attachments/20140905/3ba04b3a/attachment-0002.png>

More information about the Public mailing list