# EKS Network Policies on AWS | ZopNight

> Every check ZopNight runs on your EKS Network Policies on AWS: 1 in total, across security. Each one says why it matters and exactly what to change.

Source: https://zop.dev/zopnight/rules/aws/eks-networkpolicy

---

_AWS · 1 check_

## EKS Network Policies on AWS, checked for you.

ZopNight runs 1 check on your EKS Network Policies in AWS, covering security. Workloads are scheduled by namespace.

- 1 — check
- 1 — category
- Manual — fixes, spelled out
- Yes — scheduled with its namespace

Free to start. No card. The playground just needs your work email.

## Every check, grouped by what it protects.

Each one opens with why it matters and exactly what to change.

### Security

Risky configurations: privileged containers, containers running as root, host networking, ingress without TLS.

- [NetworkPolicy Has No Rules](https://zop.dev/zopnight/rules/networkpolicy-has-no-rules)

## Find these on your own EKS Network Policies.

Connect a read-only role and ZopNight inventories the EKS Network Policies you run, then runs its one check against them.

[object Object]