Integrate interaction server as active service into SCB

➹ New Feature implementation request

Integrate an interaction server like interactsh into the SCB

Is your feature request related to a problem?

Some scanners (e.g., Nuclei) require an interaction server to validate their findings. As a user, I may not want to use an external interaction service, as this will disclose my vulnerabilities to the operator of that server.

Describe the solution you'd like

Integrate an interaction server like interactsh into the secureCodeBox, which can be run as a service alongside the scans.

Describe alternatives you've considered

Not have an interaction service and rely on people running it themselves :(

Additional context

Considerations for a deployment which may inform the design:

• Ideally, we'd probably want a single interaction service per operator, not one per namespace, as I think each interaction server needs a domain to itself
• Consider what happens if kubernetes network policies are in place to separate namespaces.

Start by reviewing the interactsh project and secureCodeBox’s scan deployment and service entry points, then trace how Nuclei scans are configured. Define how one operator-scoped interaction service, its domain, and Kubernetes network-policy considerations should work; done means scans can use the integrated service without an external interaction provider.