Re: Communication matrix

natacha.mach@...
 

Hello,

many thanks for your feedback.
Your remark is really relevant, indeed the  “external communication” is related to “platform external” components also.
So i will add a tag regarding the hosting of TLS server or TLS client, as attached.
What do you think of this new version?

regards
natacha

De : onap-seccom@... [onap-seccom@...] de la part de Hampus Tjader [hampus.tjader@...]
Envoyé : mercredi 26 juin 2019 13:55
À : MACH Natacha TGI/OLS; onap-seccom@...
Objet : Re: [Onap-seccom] Communication matrix

Hi Natacha,

 

Great work with the matrix!

 

I have a question regarding the “external communication”. My assumption is that this category will also be used for “platform external” components, e.g say between DCAE-yyy and xNF.

Does the “communication_initiator” in this case then define the entity acting as TLS server or is it more related to who is initiating the connection (not related to TLS handshake)?  
Could be interesting to highlight this for platform-external interfaces, thus whether external facing ONAP components are hosting a TLS server or TLS client. It would also be good from a security perspective to have this inventory of platform-externally open ports for the ONAP components, so we in the future might be able to decrease the platform external attack vector.

 

Best regards,

Hampus

 

From: onap-seccom@... <onap-seccom@...> On Behalf Of natacha.mach via Lists.Onap.Org
Sent: den 25 juni 2019 16:46
To: onap-seccom@...
Cc: onap-seccom@...
Subject: [Onap-seccom] Communication matrix

 

Hello,

 

As discussed during the SECCOM of last week, i am sharing with you a proposal regarding the YAML file for the communication matrix work item.

 

Please share your comments, and then we can propose it to the PTLs.

 

Many thanks and best regards

Natacha

_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

Join onap-seccom@lists.onap.org to automatically receive all group messages.