2019
DOI: 10.2139/ssrn.3425554
|View full text |Cite
|
Sign up to set email alerts
|

A Complete Study of P.K.I. (PKI’s Known Incidents)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 13 publications
(6 citation statements)
references
References 27 publications
0
6
0
Order By: Relevance
“…A number of weaknesses have however been identified for the PKI, an academic research report authored by a team from the school of informatics and computing at Indiana University Bloomington, Software bugs and misinterpretations of industry standards accounts for 42% of incorrectly-issued SSL certificates. The research looked at 379 instances of miss-issued SSL certificates from a total of over 1300 known incidents [16].…”
Section: Literature Review and Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…A number of weaknesses have however been identified for the PKI, an academic research report authored by a team from the school of informatics and computing at Indiana University Bloomington, Software bugs and misinterpretations of industry standards accounts for 42% of incorrectly-issued SSL certificates. The research looked at 379 instances of miss-issued SSL certificates from a total of over 1300 known incidents [16].…”
Section: Literature Review and Related Workmentioning
confidence: 99%
“…This involves people, technology and processes, not everything is dependent on cryptography, [23], an employee from StartCom was able to get a domain certificate for "mozilla.com" from CertStar, a Registration Authority of Comodo. There was no validation at all at the Registration Authority in the certificate request [16].…”
Section: Cases Of Breached Pki Securitymentioning
confidence: 99%
See 1 more Smart Citation
“…Several CAs in the past have been found deviating from the guidelines and requirements regarding certificate issuance and management of private keys as set by the Certification Authority Browser (CAB) Forum [18]. A comprehensive study by Serrano et al [19] revealed notable incidents of private key exposure, which include: eight cases by Comodo, five by WoSign, four by Symantec and VeriSign, two by DigiCert, and one by DigiNotar, India CCA, Let's Encrypt, StartCom and Thawte. In most cases, operating systems and browsers distrusted CAs after publicly published incidents.…”
Section: Introductionmentioning
confidence: 99%
“…On the CA side, automation bolsters security by reducing opportunities for human error, historically a frequent cause of misissuance events [86]. The only way for Let's Encrypt to validate a domain and issue a certificate is through the normal API; there is no manual override.…”
Section: Introductionmentioning
confidence: 99%