security_monkey
security_monkey copied to clipboard
Netflix
Daily emails not sending out
The daily change notification emails do not get sent out. This will either need to be fixed or removed.
Is this still a problem? Seems to defeat the purpose of having a tool like security monkey in the first place. There hasn't been anyone else report the problem after a month either. :confused:
This is still a problem. Unfortunately, I lack the cycles to fix, so would love some help from the community.
Even if a external contributor setup a test instance of SecurityMonkey, I don't think they could reproduce this issue without being able to connect to a large collection of AWS/GCP accounts. This is a huge hurdle, so it seems highly unlikely that someone not already working at an org that uses SecurityMonkey could help.
A few suggestions that might improve the state of affairs:
- Write a detailed bug report
- Increase visibility/notoriety such as adding the label BLOCKER
- Ask other non-netflix users if they have seen the problem. Post in a SecurityMonkey mailing list, chat room, or social media
I don't agree that this requires a very large AWS or GCP setup.
At the top of my head, I think the following would need to be done:
- Set up a scheduled task that would, once a day, check for each account which users are subscribed to changes, and if there are any changes ...
- For each technology, query the database and check for change items that are <24hrs old
- Generate the email template with the diff
- Send out the emails
This feature was largely dependent on the older scheduling logic which needed to be tossed out due to massive scalability issues. While I understand that losing this feature is problematic for some users, the tradeoff was made to make Security Monkey operate massively smoother at a large scale. Addressing scalability and reliability issues with Security Monkey is currently where our priority is at.
