Decide the following:

• How to deal with the OTP tokens
• End user impact
• Information to end users
• How to deal with logs and how/who to archive (admin logs for certificates)

Note that the TSP

/Bank is responsible for handling the end user certificates through the whole process, including revoke of old certificates.

TSP or Bank

• The TSP/Bank describes the change
• Send email to Lise.Arneberg@bits.no and Torgeir.Sorvik@bits.no for approval

3) Formal order to

BankID

The respective TSP or Bank have to create and send a formal order to

BankID as an electronically signed document, signed by TSP or Bank.

This order should contain:

New RA:

• Detailed information about the CA
• Approval from BITS (from step 2)

Move or merger of RA:

• The purpose of the move or merger of the

• mentioned RA
• Detailed move or merger from and to what CA

• Approval from BITS (from step 2)

Sign it electronically and create a ticket here with the signed document attached.

The respective TSP or Bank have to fill out required order forms and send it to

BankID signed before or during the RA ceremony.

A copy must be sent before the RA ceremony.

• TSP/Bank fills out the required order form.
• Send a copy before the RA ceremony by creating a ticket here.

Order form templates can be found here: Misc forms for BankID Support

Primary CAO token "Dongle"

is normally stored in a safe at the respective TSP (CA responsible).

The respective Key Custodian for the TSP is responsible to carry and bring the RA XML request and the Primary CAO token "dongle" to the RA ceremony.

• Create an RA XML request on the TSP system, for example through HAT tool.
• Make sure that the USB stick is new and

• unused

• Make sure that the Key Custodian

• have approved identification such as a passport or driver license

• (if the Key Custodian is a non-Norwegian citizen, they must bring their passport

• )

BankID will ensure that

everything is in place and coordinate the ceremony and switchover with all stakeholders.

Check that the following is in place

:

•  BITS approval - If not provided by the TSP or Bank, contact BITS and verify
•  Formal

• order received
•  

• Signed order forms
  •  Signed - Naming of RA (Required)
  •  Signed - Revoke RA XML Request (Optional)
•  TSPs Primary CAO token
•  TSPs/Bank RA XML Request

If all is in place

, all stakeholders align and agree on date and time for the following:

•  1. RA ceremony
•  2. Activation of New RA XML Sign Certificate

•  3. Switchover 
•  4. Revoke RA XML (Optional)

Normally step 2, 3 and 4 happens within the same 24h.

BankID will send out a meeting invite for

the ceremony and the switchover.

Create and send out the invitation to all stakeholders.

The invitation should contain, but not limited to:

• Purpose and description
• Date
• Time
• Duration
• Virtual Meeting Link or Address
• Attendees and contact points
• Information on what to bring

BankID

• Participants need to sign in and out
• All necessary resources are in place
  • Key Custodian
  • PKI
  • App
• Key Custodian ID check is done by the SO
• USB virus scan is done manually before High secure room (USB stick that contains the RA XML Sign request)
• All required documentation is in place
  • Note that RA naming order forms are to be stored in the BankID High secure room

• • . When the documentation is signed

• • electronically,

• • a copy of

• • the document is to be stored

BankID is to perform the RA ceremony

BankID will guide the key custodian through issuing of the new RA XML/SSL certificate(s) on

the new CA

.

Key custodian will need to oversee that the changes made are according to the documentation.

TSP/Bank need to send a request to BankID

• Write a request for activation of New RA XML Sign certificate(s) in BankID

• .
• The request needs to contain the following:
  • Time for the activation
  • Which originator(s) to activate
  • Which CA it concerns
• Create a ticket here

BankID will coordinate with the required resources.

If not already set, agree on the date and time for:

•  1. Activation of New RA XML Sign Certificate
•  2. Switchover 
•  3. Revoke RA XML (Optional)

Normally happens within the same 24h.

BankID is to activate the new certificates

.

This is normally done during the same day as the Switchover.

Activate the new RA XML Sign certificate(s) in BankID.

Performed by AO with PKI involved.

TSP/Bank needs to check that the new activated certificate is working towards ODS. 

Check that the new certificate have access to display the existing certificates on the old CA.

Plan and implement the switchover and revoke.

1. TSP/Bank: Write a request for

1. switchover issuing CA in BankID

1. from old to New CA

1. . Include the time wanted for this. Create a ticket here
2. BankID:
   1. Do the switchover
   2. Those who perform the switchover will inform the TSP/Bank by phone when it has been done
3. TSP/Bank: Run test case sets

1.  to verify
   1. TSP/Bank: If successful, move to the next step
   2. BankID: If unsuccessful, investigate and resolve then move to next step
   3. BankID: if unsuccessful, not possible to fix, do a rollback
      • Bank/TSP: When rollback is done, run

1. 1. • test case sets

1. 1. •  to verify
2. (optional. If not done, the certificate will be active on the old CA until it expires) Bank/TSP: Send an order for

1. revoke of old RA XML Sign certificate in BankID

1. by creating a ticket here
2. (optional)

1. BankID: Revoke the old certificate

Order form templates can be found here: Misc forms for BankID Support

Renewals of end users, merchants etc.

As decided in step 1.

1. Bank renew end user BankID certificates
2. Bank asks merchants to renew merchant BankID's using HAT
3. Possible change of OTP Service by adding a new and then removing the old

This is best done outside of peak hours to reduce the risk of latencies.