Closed andresriancho closed 5 years ago
These two rules are here to highlight a different underlying issue:
TCP port open to all
highlights that a given port is accessible to all IP addresses. In practice this often creates risk if the exposed service lacks authentication or uses weak credentials.
FTP port open
highlights that a port corresponding to a known, insecure protocol is open (and maybe used?). Maybe the finding name could be revisited, but I don't think that merging both findings should happen.
Agreed and closed.
In terms of renaming I'm thinking of putting all the "X port open" issues under a single "Sensitive port open" issue.
In most cases
TCP port open to all
duplicates findings fromFTP port open
,NFS port open
, etc.If a security group opens port 21 to all, this is flagged in both
TCP port open to all
andFTP port open
. Ideally it should only be flagged inFTP port open
(which is less generic)