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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃殌 FEATURE: Automatic identification and notification for unused WAFs #365

Closed
daknhh opened this issue May 2, 2024 · 0 comments
Closed
Assignees
Labels
enhancement New feature or request

Comments

@daknhh
Copy link
Contributor

daknhh commented May 2, 2024

Is your feature request related to a problem? Please describe.
Implementing an automated identification and notification system for unused WAFs within the Firewall Factory will streamline infrastructure management, optimise costs and strengthen the security posture of the system. By leveraging Lambda capabilities and integrating with notification services, we can proactively address the challenge of WAF sprawl and ensure that resources are used efficiently.

Describe the feature you'd like
We aim to enhance the Firewall Factory system by implementing an automated process to identify and notify teams of unused web application firewalls (WAFs). This enhancement will involve the development of a lambda function that will be triggered at regular intervals, with default settings to run on the 1st of each month, but adjustable via parameters to meet varying needs. The lambda function will be responsible for identifying WAF instances that are no longer required within the infrastructure and issuing notifications to the relevant teams.

@daknhh daknhh added the enhancement New feature or request label May 2, 2024
@daknhh daknhh self-assigned this May 2, 2024
@daknhh daknhh mentioned this issue May 27, 2024
@daknhh daknhh closed this as completed May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Released
Development

No branches or pull requests

1 participant