Certification Authority

20
Certification Authority MIEIC – Segurança de Sistemas Informáticos João Brito – ei07052 João Coelho – ei07118

description

Certification Authority. MIEIC – Segurança de Sistemas Informáticos. João Brito – ei07052 João Coelho – ei07118. Contents. Theorethical introduction State of art Tecnologies review Use case scenarios. Problem. How to deploy a Certificate Authority for University of Porto? - PowerPoint PPT Presentation

Transcript of Certification Authority

Page 1: Certification Authority

Certification AuthorityMIEIC – Segurança de Sistemas Informáticos

João Brito – ei07052João Coelho – ei07118

Page 2: Certification Authority

Contents

• Theorethical introduction

• State of art

• Tecnologies review

• Use case scenarios

Page 3: Certification Authority

Problem

• How to deploy a Certificate Authority for University of Porto?

• How to provide trusted digital certificates?

• How to mantain a CRL?

Page 4: Certification Authority

Theoretical Introduction

Page 5: Certification Authority

What is a CA?

Page 6: Certification Authority

Goals

• Ensure:

• Information integrity

• User authentication

• Non-repudiation of electronic data

Page 7: Certification Authority

State of art

Technologies • OpenCA• Apache• PHP• Perl

• PHPki• Apache• PHP

• EJBCA• Java Aplication Server (JBoss)• Apache Ant (required to install)

Page 8: Certification Authority

SolutionDeployment of a CA based on EJBCA architecture.

Page 9: Certification Authority

Functionalities

• Administration

• CA creation and activation;

• Manage entities;

• Profile management;

• Public Area

• Certificate aquisition;

• Certificate revokation

check;

Page 10: Certification Authority

Deployment• EJBCA deployment• Apache Ant – configure and install EJBCA• JBoss Aplication Server – Application server that will

provide the CA service

• Administrators should install the SuperAdmin certificate to access the following URL:

• https://localhost:8443/ejbca/adminweb

Page 11: Certification Authority

User configuration• User information to certify: • Name• Address• Phone number• Email

• User details must be verified with user personal documents• Citizen card• Email/SMS secret key

Page 12: Certification Authority

Certificates

• Browser certificates• Authenticate users on faculty’s services.

Page 13: Certification Authority

• SSL/SSH Certification

Certificates

Page 14: Certification Authority

Other applications

• Certificate Signing Requests

• User uploads his public keys;

• CA retrieves certificate;

Base64 encoding

PEM format

Specific software needed

• OpenSSL

Page 15: Certification Authority

Certificate applications

• Signing information is not a functionality of this application.

• Document signing has to be done at client side.

• Examples:• Import certificate to thunderbird• Use with openssh

Page 16: Certification Authority

Signature Validation

• User list certifitates

• Entering certificate

properties:

• Issuer DN

• Certificate serial

number

Page 17: Certification Authority

Key expiration

• Certificate’s validity date should not go beyound graduation year.

• Key generation could be performed by CICA’s.

• An aternative is submission of a new key gernerated by the user and the CA should return a new digital certificate.

Page 18: Certification Authority

Revoke Lists

• The list update rate is defined by the system

administrator.

• Should be frequently updated.

• Can be obtained by anyone on public EJBCA webpage

Page 19: Certification Authority

Considerations

• Must be provided:

• Webpage documentation for the user:• Certificate creation guides• Certificate revokation guides

• Certification documentation:• Step-by-step user guide for common certification

software• For example openpgp, openssl, etc.

Page 20: Certification Authority

Thank you!

Questions?