Featuring 7 Papers as of October 29, 2015
The Scary and Terrible Code Signing Problem You Don't Know You Have
by Sandra Dunn - October 28, 2015
SSL 3.0 / TLS 1.0 certificates are built on the X.509v3 PKI standard and provide the framework that the code signing process uses. Code signing uses PKI and X.509v3 certificates issued by a trusted certificate authority to validate that the code being installed on a device comes from a trusted vendor.
Implementing Public Key Infrastructure (PKI) Using Microsoft Windows Server 2012 Certificate Services
by Michael Naish - September 16, 2014
Public Key Infrastructure (PKI) can be distilled into two critical parts: a public and a private key.
Digital Certificate Revocation
by Sally Vandeven - July 24, 2014
Secure communication on the Internet is built around the trust of digital certificates.
Building and Managing a PKI Solution for Small and Medium Size Business
by Wylie Shanks - December 23, 2013
The use of Public Key Infrastructure (PKI) can be an effective way to meet business, regulatory, and compliance requirements.
Who do you trust?
by Matthew Luallen - August 3, 2011
While certificates have their uses in a security regimen, they are not a bullet-proof method to ensure the authenticity of software, a person, or communications.
What Secure Site Seals Mean to Consumer
by Kwok Chan - October 2, 2002
We definitely trust brandname and is the key to locate the merchant in the great internet world of web sites.
Security Alert: Fraudulent Digital Certificates
by Ferdinand Gomes - June 7, 2001
Digital certificates are critical for businesses and customers who download patches, updates and various other forms of software from the Internet.
Most of the computer security white papers in the Reading Room have been written by students seeking GIAC certification to fulfill part of their certification requirements and are provided by SANS as a resource to benefit the security community at large. SANS attempts to ensure the accuracy of information, but papers are published "as is". Errors or inconsistencies may exist or may be introduced over time as material becomes dated. If you suspect a serious error, please contact email@example.com.
All papers are copyrighted. No re-posting or distribution of papers is permitted.