This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Talk:Certificate and Public Key Pinning"

From OWASP
Jump to: navigation, search
(→‎Operational considerations: new section)
Line 55: Line 55:
 
* The Internet is Broken :)
 
* The Internet is Broken :)
 
** http://blog.cryptographyengineering.com/2012/02/how-to-fix-internet.html
 
** http://blog.cryptographyengineering.com/2012/02/how-to-fix-internet.html
 +
 +
== Operational considerations ==
 +
 +
We use certificate pinning very commonly in my organization (yay for us) but we recently hit a problem when we were routinely changing a certificate on a service. The development team for one of the client applications and implemented pinning, but they had not considered what would happen when the certificate changed.
 +
 +
The majority of our clients support 2 pinned certificates at a time, so when we want to change the server cert the process is
 +
 +
1) Configure the new server cert in the client alongside the old one
 +
2) Replace the old cert on the server
 +
3) Configure the old cert from the client
 +
 +
This way we can do the cert rotation usually with no downtime for the client.
 +
 +
The team in question did not do this, which meant they had to have a few minutes of downtime (this is important as we have a demanding SLA) and also it meant that we had to do the change out of office hours to minimize the impact.
 +
 +
So, my suggestion is that we expand this page to include a section on "Operational considerations" that outlines the recommended approach.
 +
 +
Thoughts?
 +
 +
If no-one objects, I will add the new section in a couple of days.

Revision as of 11:19, 2 April 2015

Past Failures

This section is 'further reading' for those interested in surveying the landscape.

Operational considerations

We use certificate pinning very commonly in my organization (yay for us) but we recently hit a problem when we were routinely changing a certificate on a service. The development team for one of the client applications and implemented pinning, but they had not considered what would happen when the certificate changed.

The majority of our clients support 2 pinned certificates at a time, so when we want to change the server cert the process is

1) Configure the new server cert in the client alongside the old one 2) Replace the old cert on the server 3) Configure the old cert from the client

This way we can do the cert rotation usually with no downtime for the client.

The team in question did not do this, which meant they had to have a few minutes of downtime (this is important as we have a demanding SLA) and also it meant that we had to do the change out of office hours to minimize the impact.

So, my suggestion is that we expand this page to include a section on "Operational considerations" that outlines the recommended approach.

Thoughts?

If no-one objects, I will add the new section in a couple of days.

Retrieved from "https://wiki.owasp.org/index.php?title=Talk:Certificate_and_Public_Key_Pinning&oldid=192645"