Building your own honeypots
Your tenant can define honeypots of its own, built around any container image you can reach. Customize what the honeypot presents, which ports it binds and how it behaves to emulate a service, an appliance, or a version of your own software. The image stays in your own registry and the container is only ever visible to your tenant.
How they differ from Baffin Bay containers
| Baffin Bay provided | Customized | |
|---|---|---|
| Image | Built and hosted by Baffin Bay | Yours, from any registry you can reach |
| Emulation and fingerprints | Maintained and varied across the fleet for you | Yours to maintain |
| Availability | Made available to your tenant by Baffin Bay | Your tenant only |
| Editing | Not editable | Fully editable at any time |
The trade is maintenance for coverage: a provided container is kept current for you, while a container you build is only as convincing as you keep it.
Creating a custom container
In the portal, open Containers and select Create Container.
From there, follow the guided steps to create your own container.
Private images
If your image is in a private registry, add the registry credentials to your tenant first, then reference the image normally. The agent pulls it on each host using those credentials.
Using it
A custom container is used exactly like a provided one: add it to a machine profile and then every machine using the profile starts the container. See Assigning a profile.