Cryptoshop Help! Cryptoshop Contact! Cryptoshop Memo! Cryptoshop Shopping Cart! Place your order! Change to german site!
+ Products
· · · · · · · · · · · · · · · · · · · · · · ·
+ Solution
· · · · · · · · · · · · · · · · · · · · · · ·
+ Knowledge Base
  Security Targets  
  Security Governance  
  Cryptography  
  Technology  
  Smart Card applications  
  Authentication  
  PKI  
  Certificates  
  Digital Signature  
  Signature Law  
  PKI-Planning  
  How to  
· · · · · · · · · · · · · · · · · · · · · · ·
+ Service
· · · · · · · · · · · · · · · · · · · · · · ·
     
Management
· · · · · · · · · · · · · · · · · · · · · · ·
Security Officer
· · · · · · · · · · · · · · · · · · · · · · ·
System Engineer
· · · · · · · · · · · · · · · · · · · · · · ·
Purchasing
· · · · · · · · · · · · · · · · · · · · · · ·
Maintenance
· · · · · · · · · · · · · · · · · · · · · · ·
 
 

Trust models

Please note, that the Knowledge Base isn't translated to english completely at the moment. You will still find some german texts - we are translating permanently the outstanding parts! Thank you for understanding!

PKI-Planning

 
PRACTICE
 
Planning an own PKI, you have to think about many questions, about architectures, integration into existing infrastructure and applications, as well as effects on all stakeholders. Consider legal regulations as well as your own CP and CPS .





architectures

trust architecture: certification authority, certification authority certificate, trust models (cross-certifcation, Bridge-CA), hierarchy levels, registration office, registration workflow, revocation, allowed applications for user certificates
software-architecture: used applications, standards, protokols, certificate content, interfaces of services and applications,
physisal realisation and operation: certification authority, registration office, token and reader, systen administration, backup, disaster recovery and physical security, connections, evaluation


integration

existing infrastructure: already existing infrastructure, which can be used and adapted for PKI, database, directory, backup, disaster recovery,
existing applications: they have to be adapted or reconfigured for use with PKI-certificates, consider necessary certificate contents(profiles)
integration into existing processes: workflows have to be adapted.


effects on stakeholder

different user: staff, partners, supplier, customers, geographic distribution, mobility, used applications
liable for operation, support administration
guidlines, building awareness and education


Cryptoshop Tipps

PKI: Implementing and Managing E-Security Nash, Duane, Joseph, Brink
Although its written by 4 RSA experts it isn't a RSA-commercial. It contains an introduction into asymmetric cryptography, standards, applications to smart cards, biometrics and the ROI of a PKI.



Trust models


Certification hierarchy


Certification guidelines


CA - certificate compromise


Time Stamping Authority


PKI vs. PMI


PKI planing and operation


PKI deployment


PKI operation



Back to previous page!Top of page!To the startpage of Cryptoshop.com!
  Trust models  
  Certification hierarchy  
  Certification guidelines  
  CA - certificate compromise  
  Time Stamping Authority  
  PKI vs. PMI  
  PKI planing and operation  
  PKI deployment  
  PKI operation  
 
  Special offer of the month!  
  Cryptoshop Bundles!  
 
  Smart Card applications  
  MS-Enterprise-CA  
  certificate formats  
  ROI of a PKI  
  TCO of a PKI  
  CobiT-system security with PKI  
  CobiT - authenticated data administration with PKI  
  Autoenrollment  
 
Legal notice Terms and Condtitions Consumer notice Privacy Newsletter Copyright © 2004 CRYPTAS. All rights reserved