Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: Sunspot - a firewall exception request endpoint #127

Closed
jake-bladt opened this issue Dec 6, 2019 · 0 comments
Closed

Idea: Sunspot - a firewall exception request endpoint #127

jake-bladt opened this issue Dec 6, 2019 · 0 comments

Comments

@jake-bladt
Copy link

Is your feature request related to a problem? Please describe.
Conventional means of firewall management allow ingress to a system by IP address range and port. This is fine if you know in advance where your calls into the system will be coming from. With orchestration (and particularly functions as a service,) the potential subnet can be vast and insecure. For example, Azure Functions require you to open your port to an entire Azure data center. Any bad actor who wants to attack your system can do so using an Azure function in the same region as yours.

Describe the solution you'd like
Sunspot is a system that listens on a single HTTPS endpoint for requests that include an originating IP address, a port, a time span, and a previously-distributed secret. When it receives a valid request, it creates a firewall exception for that port and a scheduled job to remove that exception once the timespan expires.

Describe alternatives you've considered
The most obvious alternative is to open up to a wider subnet and require the clients to pass a secret
with each call. This works all right with programmed RESTful endpoints, but is inelegant for opening ports to databases, etc.

Additional context
This is something I'd like to build and open source myself, but probably won't get to in the foreseeable future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants