-
Bug
-
Resolution: Won't Do
-
High
-
None
-
Frankfurt Release
in the daily HTTP public port scan, we still can see 2 ports open for Portal
log-kibana 30253/tcp open http Elasticsearch Kibana 5.5.0
log-es 30254/tcp open http Elasticsearch REST API 5.5.0 (name: AenJYr2; cluster: onap-log; Lucene 6.6.0)
log-ls 30255/tcp open unknown
As it represents a possible security issue, HTTP port must be the exception and motivated to be put in a white list.
If not, such ports must be removed.
Note I have assigned the Jira to dmcbride as I am not sure that Prudence (referenced in the INFO.yaml) is still managing Logging project.