Beacons
Deploying and managing beacons to extend surface visibility into internal networks
A Beacon is a component deployed inside a client's internal network that gives Ethiack access to assets that would otherwise be unreachable from the outside. This allows Hackian to run the same tests performed on external surfaces against assets sitting on internal networks, extending your coverage beyond the public perimeter. Beacons use outbound-only connectivity, so no inbound firewall rules are required on your side.
Deploying a new beacon
Clicking Add opens the step-by-step deployment instructions. Several deployment methods are supported — Quick Install (curl script), Ansible, Kubernetes, and Helm — so you can choose the approach that fits your infrastructure. The full instructions are also available at Configuring your Beacon.
Beacon list
The Beacons tab shows all beacons registered for your organization. For each beacon the following information is displayed:
| Field | Description |
|---|---|
| Name | The identifier given to the beacon |
| Endpoint type | The deployment type, e.g. VM or Kubernetes |
| CIDR ranges | The internal network ranges the beacon has access to |
| DNS server | The DNS server the beacon is configured to use |
| Status | Whether the beacon is active and reachable |
| Last communication | When the beacon last checked in |
| Registered | When the beacon was first added to your organization |
