...
This page contains service description outlining how and where service should be used, targeted users, service delivery model and service elements and topology. RESPONSIBLE: Information provided in this page is initially populated by the development team (during the transition phase), and revised based on the need or in a yearly service check by Certificate Transparency (CT) Service Manager, with exception of CBA which remains the responsibility of business development team. |
Service description
Add brief description of the service, how and where service should be used, typical or key use cases or scenarios (for various groups/levels of end users) and other relevant overview information
Users
Certificate Transparency (CT) log service
Used by Certification Authorities (CA:s) to log issued certs in.
Used by web browsers to verify that certificates are publicly logged.
Used by browser vendors for proof of certificate mis-issuance.
Users
CT logs are part of the web security infrastructure on the internet, ultimately strengthening trust in domain certificates by catching "lying CA:s".
UseCases/UserStories: ct_user_stories.txtAdd definition of who are the targeted users, estimate about possible number of users etc.
Contacts
All operations, business development and stakeholders contacts
...
| Service Manager | Deputy Service Manager | L1 support | L2 support | L3 support |
|---|---|---|---|---|
Service delivery model
Add explanation about organisation of service deliveryCT logs are accessed over HTTP on the public internet.
Service Elements
Service Elements, with brief description and links to products, resource instances and software stack of the service, indicating the software components types - if they are internally (in-house) developed, OSS or commercial off-the-shelf software. Service elements can be grouped in two following categories:
Technology infrastructure
Add list and description of products and resources used to deliver main functionalities of the service. Add service technical architecture - i.e. its good to have a conceptual architectural diagram and topology diagram.
Supporting infrastructure
...
- In-house developed OSS "catlfish"
View file name catlfish-system-2.pdf height 250 View file name urd-topology.pdf height 250
Supporting infrastructure
- Systems and service operations framework for deployment and orchestration
- Monitoring system for checking the health of systems and services and generating alarms
- Hardware Security Module (HSM) infrastructure forkeeping sensitive keys off of general purpose computer
Cost Benefit Analysis
Provide URL to last valid CBA
CBA draft documents can be found as attachements in
(restricted access)