...
It should be reviewd at each major release of the component.
As all projects already exist:
- first external flow should be specified.
- then proceed with inter-components flows.
- Intra-component flows
The 2 first steps are important to gather relevant information to build the access control strategy of ONAP platform.
HOW a flow matrix?
This may be too complicated to address all flows for a given project.
...
This file enables to provide information for each external flow for the DCAE example:
| Parameter | Value |
|---|---|
| name | name of the ONAP project e.g. DCAE. |
| sub_components: - name: | real name of the sub component e.g. dcae-snmptrap-collector |
| external_server_side: | in external server side list only ingress (external -> ONAP) traffic |
| type: | nodePort |
| external_communication: | N/A |
| description | e.g. SNMP trap |
| id | e.g. DCAE_EXT_1. |
| communication_initiator | which component initiates the communication. e.g. any component sending SNMP either internally to ONAP platform or externally e.g. xNF. |
| communication_receipt | which component is the dest of the communication. |
| protocol | at least level 4 or higher, to be specified if applicable. |
| version | to be specified if applicable |
| exposed_pod_port | to be specified if applicable |
| exposed_port | to be specified if applicable |
| encryption | none or active e.g. |
| HTTPS implemented. | |
| data_exchanged | |
#
exposed_pod_port: 6162 #to be specified if applicable
exposed_port: 30470 #to be specified if applicable
encryption: none
#data_exchanged: specifies the file format, the main exchanged information.
data_exchanged: snmp trap information
#to specify whether the component hosts a TLS sever or a TLS client (yes or no), if applicable.
tls_server: N/A
tls_client: N/A
flow_direction: incoming
...