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

Backup encryption required for firewalls with a subscription #1019

Open
cotosso opened this issue Jan 14, 2025 · 1 comment
Open

Backup encryption required for firewalls with a subscription #1019

cotosso opened this issue Jan 14, 2025 · 1 comment

Comments

@cotosso
Copy link
Contributor

cotosso commented Jan 14, 2025

Firewalls with active subscription currently send their backup to Nethesis Operation Center, regardless the fact they are encrypted or not.
To promote best practices in cybersecurity measures and enhance data protection I propose to send backups only if they are encrypted with a passphrase.

Proposed solution
Ensure backups are transmitted to the Service Center only if they are encrypted.

If the firewall has an active subscription and the passphrase is not configured:

  • Display a notification in the Dashboard informing the user that backup transmission is currently suspended.
  • Send information to the Nethesis Operation Center indicating whether the passphrase is configured or not (there is already an issue for that: Inventory: add backup passphrase status (set/unset) #988)
@cotosso cotosso added this to the NethSecurity 8.5 milestone Jan 14, 2025
@cotosso cotosso moved this to ToDo 🕐 in NethSecurity Jan 14, 2025
@gsanchietti
Copy link
Member

Current proposal has some drawbacks:

  • Operational Disruptions: Users who haven't set a passphrase for encryption might experience disruptions in their backup routines, leading to potential data loss if they're unaware of these new requirements.
  • User Experience: Forcing users to configure a passphrase might add complexity and inconvenience, especially for those who may not be familiar with encryption practices or have not previously used them.
  • Support Overhead: Implementing this change might increase the support burden, as users may require assistance with configuring encryption and troubleshooting any issues that arise from the new policy.
  • User Awareness: After this change is in place, users who haven't connected to a firewall for a while may not realize that the configuration must be fixed, leading to confusion and potential lapses in backup coverage.

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

No branches or pull requests

2 participants