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

Create a mapping of Secure by Design requirements #329

Open
2 of 20 tasks
mitchelbaker-cisa opened this issue Jun 5, 2024 · 0 comments
Open
2 of 20 tasks

Create a mapping of Secure by Design requirements #329

mitchelbaker-cisa opened this issue Jun 5, 2024 · 0 comments
Assignees
Milestone

Comments

@mitchelbaker-cisa
Copy link
Collaborator

mitchelbaker-cisa commented Jun 5, 2024

Is your feature request related to a problem? Please describe.

Create a mapping of Secure by Design requirements and how these relate to new features planned for LME 2.0.

Describe the solution you'd like

Secure by Design principles:

  • Memory safe programming languages (Go, Python, Podman and memory safe containers?)
  • Secure Hardware Foundation
  • Secure Software Components
  • Web template frameworks (N/A) (does elastic have preventative measures against XSS)
  • Parameterized queries
  • Static and dynamic application security testing (SAST/DAST)
  • Code review
  • Software Bill of Materials (SBOM)
  • Vulnerability disclosure programs
  • CVE completeness
  • Defense-in-depth
  • Satisfy Cybersecurity Performance Goals (CPGs)

Secure by Default principles:

  • Eliminate default passwords
  • Mandate MFA
  • SSO
  • Secure logging
  • Software authorizatino profile
  • forward-looking security over backwards compatibility
  • track/reduce "hardening guide" size
  • Consider user experience consequences of security settings

Additional context

Secure by Design pdf

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

No branches or pull requests

2 participants