Avamprogetto 2a

Technical requirements for the handover interfaces for the execution of telecommunications surveillance

CSP PTSS

Admin. Admin.

Function Function

Adm. Adm.

Activation Order

(e-mail)

Encryption: KCpub1 and KPpub1

Signed: KPpr11

Subject: Interception Type & reference

Content: XML (HI-1, Create Request, LITask)

+ Order form

Order reception confirmation

Encryption: KPpub1 and KCpub1

Signed: already signed

2 Subject: Re: Interception Type &

reference

Content: None

Confirmation of execution

Encryption: KPpub1

Signed: KCpr1

3 Subject: Re: Interception Type &

reference

Content: XML (HI-1, Create Response, LITask)

+ Order form

Acknowledgement of confirmation of execution

Encryption: KCpub1 and KPpub1

Signed: already signed4

Subject: Re: Re: Interception Type &

reference

Content: none

Used OpenPGP keys:

KPpub1 = public key from PTSS / KPpr1= private key from PTSS

KCpub1 = public key from CSP / KCpr1= private key from CSP

Figure 4-12: Message flow for email activation order processing for real-time interceptions

 PTSS sends an email with the interception order. The order is an activation order using the CREATERequest action in the XML (see details in section 4.3.3.1.5). The body and the attachments of the email are signed and encrypted with the OpenPGP keys.

 CSP confirms the reception of the secure email order by sending back the received email body but without the attachments. The email's original subject is prefixed with the Re:

denoting a response. No signing and encryption is necessary for this step as the original email was already signed and encrypted.