Changes

Jump to: navigation, search

Security/Features/CA Policy Constraints in Code

875 bytes added, 00:40, 10 December 2013
Created page with "{{FeatureStatus |Feature name=CA Policy Constraint Checking in Code |Feature stage=Draft |Feature health=OK }} {{FeatureTeam |Feature product manager=Sid Stamm |Feature additi..."
{{FeatureStatus
|Feature name=CA Policy Constraint Checking in Code
|Feature stage=Draft
|Feature health=OK
}}
{{FeatureTeam
|Feature product manager=Sid Stamm
|Feature additional members=Kathleen Wilson
}}
{{FeaturePageBody
|Feature overview=https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AroPYigJXMK4dDZBcWQ1bTd6eVRoZ3hFQ1JyUk5iRGc#gid=0

We should check key constraints (and other constraints) recommended by our [http://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/ CA Policy] and the CAB Forum Baseline Requirements as checks in PSM.
|Feature users and use cases=We can automatically detect and block unsafe configuration of certificates and HTTPS connections that are weak.
}}
{{FeatureInfo
|Feature priority=P2
|Feature theme=TLS Hardening
|Feature roadmap=Security
|Feature engineering team=Security
}}
{{FeatureTeamStatus}}
Canmove, confirm
1,537
edits

Navigation menu