SAMMY UI is optimized for resolutions with a width 1024px and higher.
DSOMM
Browse DSOMM
I-IH-1-1: MFA for admins
I-IH-1-2: Simple access control for systems
I-IH-1-3: Usage of edge encryption at transit
I-IH-2-1: Applications are running in virtualized environments
I-IH-2-2: Backup
I-IH-2-3: Baseline Hardening of the environment
I-IH-2-4: Isolated networks for virtual environments
I-IH-2-5: MFA
I-IH-2-6: Usage of an security account
I-IH-2-7: Usage of encryption at rest
I-IH-2-8: Usage of test and production environments
I-IH-2-9: Virtual environments are limited
I-IH-3-1: Filter outgoing traffic
I-IH-3-2: Immutable infrastructure
I-IH-3-3: Infrastructure as Code
I-IH-3-4: Limitation of system events
I-IH-3-5: Role based authentication and authorization
I-IH-3-6: Usage of internal encryption at transit
I-IH-3-7: Usage of security by default for components
I-IH-3-8: WAF baseline
I-IH-4-1: Hardening of the Environment
I-IH-4-2: Production near environments are used by developers
I-IH-4-3: Usage of a chaos monkey
I-IH-4-4: WAF medium
I-IH-5-1: Microservice-architecture
I-IH-5-2: WAF advanced
Usage of security by default for components
I-IH-3-7: Usage of security by default for components
  • Hardening of components is important, specially for image on which other teams base on. Hardening should be performed on the operation system and on the services inside (e.g. Nginx or a Java-Application).