Add Security Best Practices Section to DISCOVER Cookbook

[Susmita331]

This PR adds a Security Best Practices section to the DISCOVER Cookbook. It offers clear guidance on data privacy, handling backups, setting up firewalls, and using tools like netcat safely. These updates aim to help event organizers and technical users improve security with practical, easy-to-follow steps.

[aterrel]

1. I don't think this page as written fits with the tone and depth of the guide. Would rather see something more along the lines of requirements for technical systems.
2. Additionally the title is a bit misleading as the article is about "cybersecurity" which is important, but when I saw "security" I was thinking "physical security", i.e. how to have guards etc.
3. Would move this to higher in the guide so contributing stays the last section.

[aterrel]

This section seems out of place. Please remove.

[aterrel]

The rest of the guide really doesn't dive into technical details of registration and web systems. I think this advice here is so overly vague as to not be helpful. Perhaps a better approach would be to provide checklist of features required by any conference web system.

[Susmita331]

Dear Andy, Thank you for reviewing my pull request and providing valuable feedback. I appreciate the time and effort you’ve taken to offer detailed suggestions for improvement. I understand your concerns regarding the tone, depth, and alignment of the content with the project’s overall structure. Based on your recommendations, I will work on refining the technical details, clarifying the scope of security, and incorporating a practical checklist for event management systems. I’ll also ensure that the revised content better aligns with the guide’s standards. Please let me know if there are any specific areas you’d like me to focus on further. Thank you for your guidance and support. I’ll notify you once I’ve made the necessary updates. Regards Susmita

…

On Wed, 15 Jan 2025 at 05:46, Andy R. Terrel ***@***.***> wrote: ***@***.**** requested changes on this pull request. 1. I don't think this page as written fits with the tone and depth of the guide. Would rather see something more along the lines of requirements for technical systems. 2. Additionally the title is a bit misleading as the article is about "cybersecurity" which is important, but when I saw "security" I was thinking "physical security", i.e. how to have guards etc. 3. Would move this to higher in the guide so contributing stays the last section. ------------------------------ In DISCOVER/15_security_best_practices.md <#155 (comment)> : > + - Protect your data with secure cloud storage solutions. + - Recommended services: + - [Backblaze](https://www.backblaze.com/) (Cloud backup for full systems). + - [Google Drive](https://drive.google.com/). + - [Dropbox](https://www.dropbox.com/). +- **Follow the 3-2-1 Backup Rule**: + - Keep **3 copies** of your data: 1 primary and 2 backups. + - Use **2 different storage types** (e.g., external drive and cloud). + - Store **1 copy offsite** to ensure data safety in case of disasters. + +- **Automate Your Backups**: + - Schedule regular backups (daily, weekly, or monthly) to ensure all new files are saved. + +- **Test Your Backups Regularly**: + - Periodically check that your backup files are complete and can be restored without errors. +# `netcat`: A Powerful Network Tool to Use with Caution This section seems out of place. Please remove. ------------------------------ In DISCOVER/15_security_best_practices.md <#155 (comment)> : > @@ -0,0 +1,109 @@ +# Ensuring Privacy and Security in Event Management + +Maintaining robust data privacy and security practices is crucial for safeguarding attendee information and ensuring a successful, trustworthy event. + +## The Importance of Privacy in Events + +Event organizers often collect sensitive attendee information, such as contact details, dietary restrictions, and accessibility needs. Protecting this data builds trust, enhances reputation, and ensures compliance with regulations like GDPR (General Data Protection Regulation) and CCPA (California Consumer Privacy Act). + +## Practical Security Measures + +1. **Protect Online Forms** The rest of the guide really doesn't dive into technical details of registration and web systems. I think this advice here is so overly vague as to not be helpful. Perhaps a better approach would be to provide checklist of features required by any conference web system. — Reply to this email directly, view it on GitHub <#155 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOIQJXR2E3YR2QINNEHIDM32KZKARAVCNFSM6AAAAABVBLZIIWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKNJSGYYTEMRRGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>