|
1
|
|
|
2
|
- Authentication
- Identity of originator confirmed
- Non-Repudiation
- Originator cannot disavow transaction
- Integrity
- Information has not been altered
- Confidentiality
- Content hidden during transport
|
|
3
|
- Privacy and Confidentiality
- Secure Transport
- File Encryption
- Secure e-mail
- Authentication
- Network components & end users
- Non-repudiation and Data Integrity
- Digital signature
- Trusted time stamp
|
|
4
|
- Subscribers
- Hold private key, use certificates for digital signature,
authentication, receipt of secure e-mail
- Relying Parties
- Rely on certificates, validate signatures, authenticate system users,
send secure e-mail
- Certification Authority
- Authenticate subscribers, issue & manage certificates, publish CPS,
publish certificate status for relying parties
|
|
5
|
- Certificate Policy
- Defines requirements and standards for issuance and management of keys
and certificates and the obligations of all PKI entities
- Used to determine level of trust the certificate affords
- Certification Practice Statement
- Defines specific practices employed by CA for issuance and management
of keys and certificates
- Used for accreditation
- Policy Interoperability
- CP and CPS have standard format & content
- Facilitates policy mapping between PKIs
|
|
6
|
|
|
7
|
|
|
8
|
|
|
9
|
- What (document)
- WYSIWYS = What You See Is What You Sign
- Why (intent)
- Declarative statement within signing ceremony
- Who (authentication)
- Certificate binds individual to keys
- Certificate Policy defines trustworthiness of identity
- When (non-repudiation)
|
|
10
|
- Issued by Certificate Authority
- Provides trust in identity by linking keys to individual or organization
- Method used authenticate identity
- Security of CA infrastructure
- Procedures and practices for life-cycle management
- Level of Assurance is dependant upon all of these variables
- Certificate Policy defines Levels of Assurance
|
|
11
|
- Why is the Certification Authority important?
- Entity that ‘vouches’ for subscriber identity
- Entity that is potentially liable for trust decisions made by relying
parties
- Why is subscriber authentication important?
- Primary basis for trust between parties
- Level of trust dependent upon method of authentication
|
|
12
|
|
|
13
|
- Needed if Certificates are used outside the Enterprise
- Hierarchical PKI with common trust anchor
- Intrastate – State Root Authority
- Interstate – Federal Root Authority
- Cross Certification another option
- Possible only if policies can be mapped
- Federal Bridge
|
|
14
|
- Return on investment
- Restrictive use
- Perceived technical complexity
- Labor intensive support
- In-House vs. Outsource
- Speed of deployment
|
|
15
|
- Legal
- Policies, Liability, Cross Certification, …
- Organizational
- Registration, Distribution, Revocation, Help Desk, Training
- Operational
- Secure Data Centers, Disaster Recovery, Audits
|
|
16
|
- HIPAA
- Homeland Security
- eGovernment and eCommerce
- Paperwork Reduction
- Application Modernization
|
|
17
|
- Certificates that are accepted nationwide for government, commercial,
and financial transactions
- A trusted CA with strong internal controls over issuance, distribution,
and management
- Policies that are enforceable nationwide
- An issuer that will not go out of business
- Liability protection
- Reasonable pricing
|
|
18
|
- A Federal Government Issued Certificate
- Common legal and policy framework
- Useable and enforceable nationally
- Economies of scale for cost of operations
- Could bridge internationally to other nationally endorsed Certificate
Authorities
- Not a National ID-Card
- Privacy protection
- Participation optional
|