daniel_sagi faa7571127 1. Added an --active flag, to allow optional "Proof" result, which will do an active hunting of a found vulnerability ...

2. Added a --remote flag to specify remote clusters/machines for hunting.
3. Improved a bit of the architecture, (Services)

Note:
The reporter module, will gather vulnerabilities before their active hunting will start.
This is not an issue, as we can access all of the attributes of the event directly from the active hunter (event.previous), which we will proccess on the end in the report

2018-06-10 19:34:12 +03:00

log

1. Added an --active flag, to allow optional "Proof" result, which will do an active hunting of a found vulnerability

2018-06-10 19:34:12 +03:00

modules

1. Added an --active flag, to allow optional "Proof" result, which will do an active hunting of a found vulnerability

2018-06-10 19:34:12 +03:00

.dockerignore

1. Added --pod flag to option "from pod" hunting. this will hunt the internal subnet of the cluster.

2018-06-06 10:08:02 +03:00

.gitignore

Added .gitignore file, ignoring .pyc files,

2018-05-13 17:16:51 +03:00

Dockerfile

1. Added --pod flag to option "from pod" hunting. this will hunt the internal subnet of the cluster.

2018-06-06 10:08:02 +03:00

kube-hunter.py

1. Added an --active flag, to allow optional "Proof" result, which will do an active hunting of a found vulnerability

2018-06-10 19:34:12 +03:00

requirements.txt

1. completely transferred all event types to their corresponding module

2018-06-10 16:43:05 +03:00

Description

Hunt for security weaknesses in Kubernetes clusters

hacktoberfestkubernetes-clustersvulnerabilities

Apache-2.0 3.1 MiB

Languages

Python 99.2%

Makefile 0.5%

Dockerfile 0.3%