security - When is it acceptable to use self-sign cert in production? -
self signed cert looked down test-only certificate. per understating, using production fine if used right reason. trying provide guidelines customers use what. e.g.:
- authentication: not ok use self-signed brower not trust "self" issuer. so, service-to-service or service-to-client authentication not ok use self-signed. unless there pre thumbprint/cn whitelisting process before verifying. lot of people these, e.g. azure upload management cert public key, used authenticate api.
- signing: no ok, there no trust issuer. unless there pre thumbprint whitelisting process before verifying. unless there pre thumbprint/cn whitelisting process before verifying.
- encryption: ok use self-signed there no chain trust required. in case of attack, mim cert not decrypt, no other impact.
i thoughts/recommendations/guidelines community ensure recommendations in right direction.
thanks.
authentication: not ok use self-signed brower not trust "self" issuer.
ok use long there trusted offline certificate distribution process. not ok use via 'trust-all' code.
signing: no ok, there no trust issuer.
ok use long there trusted offline certificate distribution process.
encryption: ok use self-signed there no chain trust required. in case of attack, mim cert not decrypt, no other impact.
ok use long there trusted offline certificate distribution process. part 'mi[t]m cert not decrypt' meaningless. certificates don't perform decryption, , mitm has managed provide own certificate instead of target's have corresponding private key, otherwise attack pointless. in absence of trust, if sender uses public key out of untrusted certificate encrypt anything, doesn't know can decrypt it, being insecure.
Comments
Post a Comment