Outpost
Some of what you need scanned is not on the internet, and some of it should never leave your network. A GitLab server on a private address, a Harbor registry behind the firewall, a token that only works from your office's IP range, an AWS account whose security team will not let an outside account assume a role in it. Dwaar's own scan plane cannot reach any of that, and for some of it, your policies say it must not try.
An outpost is a small runner you install inside your network. It connects out to Dwaar, takes the work of the connections you bind to it, and does that work next to your systems. Dwaar still plans every scan and turns every result into findings. An outpost changes where the work runs, not what you see.
What an outpost is
| An outpost is | An outpost is not |
|---|---|
| A single program, the Dwaar Outpost, on a Linux host with Docker, or a task on AWS ECS with EC2 capacity. | A copy of Dwaar. Planning, findings, triage, reports and every page of the console stay in Dwaar. |
| Outbound only. It calls Dwaar for work; nothing calls it. | A tunnel or a VPN. Dwaar cannot open a connection into your network through it. |
| A place where three kinds of work run: discovery, connection tests and scans. | A general purpose agent. It runs only Dwaar's analyzers, only for connections bound to it. |
| Yours. You pick the host, you run it, you patch it, you revoke it. | Managed by Dwaar. Dwaar never logs in to it and cannot upgrade it. |
| One outpost for one Dwaar tenant, with a credential of its own. | Shared. An outpost cannot take work from two tenants. |
The work it takes
An outpost runs three kinds of work, and only for connections bound to it:
| Work | What runs on the outpost | Where you see it |
|---|---|---|
| Discovery | Listing what the connection can see: repositories, images, refs, cloud resources. The same code Dwaar would run, in the outpost's own process. | Scan Center, Queue, with Runs on naming the outpost. |
| Connection test | Test connection, the check before a connection is saved, and the preview of what discovery would find in the connect form. | The connect form and the connection's page. |
| Scan | Every scan of a resource that connection discovered: a checkout or image pull, then the analyzers, each in its own container on the outpost's host. AWS account and GitHub organization posture checks too. | Scan Center, Queue, with Runs on naming the outpost. The resource's Scans tab lists the same scans, but not where they ran. |
Connections you do not bind keep running on Dwaar. One account can have both, and most do.
What changes for you, and what does not
Once a connection is bound, almost nothing about how you work changes.
| Stays the same | Changes |
|---|---|
| Findings, their triage, waivers, reports, products and lineage. | Where discovery, tests and scans of that connection run. |
| The connection's discovery settings, scanning triggers and scanner categories. | The checkout and the image layers never leave your network. |
| Rescans, forced rescans, cancelling from the queue. | A connection whose outpost is down cannot be discovered or tested until it is back. |
| Who may see and change the connection. | You own a host: its size, its patches, its network rules. |
Why you would need one
Bind a connection to an outpost when any of these is true:
| Situation | Why Dwaar alone cannot do it |
|---|---|
| The source host or registry has a private address | Dwaar's scan plane never reaches private, loopback or link-local addresses. A GitHub Enterprise Server, a self managed GitLab, or a Harbor, Nexus or Artifactory registry inside your network is invisible to it. |
| The token only works from your IP addresses | The provider refuses calls from Dwaar's network, and a refused call can trip your own alerting. |
| Your code or images must not be copied out of your network | Without an outpost, Dwaar checks out the code and pulls the images in its own scan plane. With one, the checkout and the layers stay on your host and are deleted when the scan ends. |
| An AWS account must not trust an outside account | Without an outpost, the role trusts Dwaar's account. With one, it trusts the outpost's own role in your account, and no AWS credential of yours exists outside it. |
When you do not need one
If none of those applies, do not deploy an outpost. A connection to github.com, GitLab.com, Docker Hub or an AWS account you are happy to have trust Dwaar is simpler without one: nothing to size, patch or watch, and no host that can be down at 3am.
Be honest about the third row in particular. "Code must not leave the network" usually means "the source must not be copied out". An outpost does that. It does not mean nothing about the code reaches Dwaar: the analyzers' results do, and a code finding carries the lines it points at. Read What stays and what goes before you promise your security team more than an outpost gives.
If you are not sure
Answer these in order. The first yes decides.
- Can Dwaar's Test connection reach the provider at all? If it fails with Unreachable and the address is private, you need an outpost.
- Is the token restricted to your IP addresses? You need an outpost, and you should turn on Only reachable from the outpost too.
- Does a written policy forbid copying this source or these images out of your network? You need an outpost.
- Does your AWS security team refuse roles that trust an outside account? You need an outpost for those AWS connections only.
- None of the above? Run the connection on Dwaar. You can bind it to an outpost later without recreating it.
In this section
| Page | Read it when |
|---|---|
| How an outpost works | You want the data flow, how jobs move, and what happens when an outpost goes away. |
| Choose a deployment | You are deciding between systemd, Docker, Compose and AWS ECS, how many outposts, and where. |
| Plan an outpost | You are sizing a host and talking to your network team. |
| Deploy an outpost | You are installing one on a Linux host with systemd, Docker or Compose. |
| Deploy on AWS ECS | You want it in an AWS account, created by a CloudFormation stack. |
| Bind connections | It is online and you want work to run there. |
| Operate an outpost | You are watching, upgrading, revoking or replacing one. |
| Security model | Your security team has to sign off on it. |
| Troubleshooting | Something is refused, offline or stuck. |
| Outpost FAQ | An evaluation raised a question: Fargate, Kubernetes, Windows, air gaps, cost. |
Try this next
List the connections you could not add because Dwaar could not reach them, or that you added with a token broader than you liked. Pick the one that matters most, read Plan an outpost, and deploy a single outpost for that connection alone. One bound connection that scans cleanly tells you more than any diagram.