Container orchestration framework aware port scanning

A system, comprising:

• one or more nodes configured to run processes;
• a scanner service;
• a container management service configured to manage a set of services by allocating managed containerized processes associated with the set of services to the one or more nodes;
• wherein the scanner service is configured to:
• identify a first node of one or more nodes associated with a container management service;
• determine a first container identifier associated with a first managed container;
• scan the first managed container for vulnerabilities;
• identify a second process running on a second open port;
• determine a second container identifier associated with a second managed container;
• determine whether the first container identifier corresponds to the second container identifier;
• in accordance with determining that the first container identifier does not correspond to the second container identifier, scan, by the scanner service, the second managed container for vulnerabilities;
• and
• in accordance with determining that the first container corresponds to the second container identifier, determine, by the scanner service, to forgo scanning the second managed container.

One or more non-transitory computer-readable medium comprising computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

• identifying, by a scanner service, a first node of one or more nodes associated with a container management service, the container management service configured to manage a set of services by allocating managed containers associated with the set of services to the one or more nodes, and the scanner service configured to identify vulnerabilities of processes running on the one or more nodes;
• determining, by the scanner service, a first container identifier associated with a first managed container;
• scanning, by the scanner service, the first managed container for vulnerabilities;
• determining, by the scanner service, a second container identifier associated with a second managed container;
• determining, by the scanner service, whether the first container identifier corresponds to the second container identifier;
• in accordance with determining that the first container identifier does not correspond to the second container identifier, scanning, by the scanner service, the second managed container for vulnerabilities;
• and
• in accordance with determining that the first container identifier corresponds to the second container identifier, determining, by the scanner service, to forgo scanning the second managed container.