Code of Conduct

Rules for building vibrant and useful communities

                       

Overview

• All group members should follow
• Summary
• Reporting
• More examples
• More on Security

Code of Conduct statements define rules to protect communities and their members from those who seek to judge, shame, and destroy.

The rules define how we treat each other so that everyone feels welcomed, comfortable, and safe.

Microsoft published Code of Conduct examples, which group members agree to follow as conditions for admittance.

From the Code of Conduct for Azure Data Tech Groups at

https://opensource.microsoft.com/codeofconduct

All group members should follow

Throughout each interaction:

• Be friendly and welcoming
  • Listen with purpose and create space for others’ communication preferences.
  • Ask yourself how you can make someone’s life easier.
• Be patient
  • Remember that people have varying communication styles and preferences.
  • Recognize that not everyone is using their native language. Meaning and tone can be lost in translation.
• Be thoughtful
  • Think about how others will interpret your words. Aim for clear and productive communication.
  • Remember that sometimes it is best to refrain from commenting.
• Be respectful and inclusive
  • Respect differences of opinion.
  • Seek to understand and build bridges, not condemn or criticize.
  • Make a conscious effort to include people who differ from you.
• Be open and curious
  • Assume good intent and interpret others’ statements or questions in good faith.
  • Ask questions to understand, not denounce.
  • Focus on continuous learning. Improve upon the things you already know, tackle new things, and ask others about their expertise to deepen your own knowledge.

Summary

• Treat everyone with respect, kindness, and empathy.
• Use welcoming and inclusive language.
• Be thoughtful in how you communicate in person and online.
• Don’t be destructive or inflammatory.
• Gracefully accept constructive criticism.
• Listen with purpose and create space for others’ communication preferences.
• Reach out to the organizers if you need anything.

Reporting

• Please report any concerns, suspicious activity, or disruptive behavior to the Azure Data Tech Groups team at ms-data@microsoft.com.

More examples

https://www.pelham.ca/en/living-here/resources/Documents/S100-12—Public-Code-of-Conduct.pdf

---

More on Security

This is one of a series on Security and DevSecOps:

1. Security actions for teamwork and SLSA

2. DevSecOps

3. Code Signing on macOS

4. Transport Layer Security

5. Git Signing
6. GitHub Data Security

7. Encrypt all the things

8. Azure Security-focus Cloud Onramp

9. Azure Networking

10. AWS Onboarding
11. AWS Security (certification exam)
12. AWS IAM (Identity and Access Management)

13. AWS Networking

14. SIEM (Security Information and Event Management)
15. Intrusion Detection Systems (Goolge/Palo Alto)

16. Chaos Engineering

17. SOC2
18. FedRAMP

19. CAIQ (Consensus Assessment Initiative Questionnaire) by cloud vendors

20. AKeyless cloud vault
21. Hashicorp Vault
22. Hashicorp Terraform

23. OPA (Open Policy Agent)

24. SonarQube
25. WebGoat known insecure PHP app and vulnerability scanners

26. Test for OWASP using ZAP on the Broken Web App

27. Security certifications

28. Details about Cyber Security

29. Quantum Supremecy can break encryption in minutes
30. Pen Testing

31. Kali Linux

32. Threat Modeling
33. WebGoat (deliberately insecure Java app)

---