Obmondo logo
  • Why Obmondo
  • Scope of Service
  • Compliance
  • Pricing
  • Features
LoginSignup
Close
  • Why Obmondo
  • Scope of Service
  • Compliance
  • Pricing
  • Features
  • GitHub
LoginSignup
    • Overview
    • 8.1 User Endpoint Devices
    • 8.2 Privileged Access Rights
    • 8.3 Information Access Restriction
    • 8.4 Access to Source Code
    • 8.5 Secure Authentication
    • 8.6 Capacity Management
    • 8.7 Protection Against Malware
    • 8.8 Management of Technical Vulnerabilities
    • 8.9 Configuration Management
    • 8.10 Information Deletion
    • 8.11 Data masking
    • 8.12 Data leakage prevention
    • 8.13 Information backup
    • 8.14 Redundancy of information processing facilities
    • 8.15 Logging
    • 8.16 Monitoring activities
    • 8.17 Clock synchronization
    • 8.18 Use of privileged utility programs
    • 8.19 Installation of software on operational systems
    • 8.20 Networks security
    • 8.21 Security of Network Services
    • 8.22 Segregation of Networks
    • 8.23 Web filtering
    • 8.24 Use of Cryptography
    • 8.25 Secure Development Life Cycle
    • 8.26 Application Security Requirements
    • 8.27 Secure System Architecture & Engineering Principles
    • 8.28 Secure Coding
    • 8.29 Security Testing in Development and Acceptance
    • 8.30 Outsourced Development
    • 8.31 Separation of Development, Test, and Production Environments
    • 8.32 Change Management
    • 8.33 Test Information Security
    • 8.34 Protection of Information Systems During Audit Testing
      • Overview
      • 8.1 User Endpoint Devices
      • 8.2 Privileged Access Rights
      • 8.3 Information Access Restriction
      • 8.4 Access to Source Code
      • 8.5 Secure Authentication
      • 8.6 Capacity Management
      • 8.7 Protection Against Malware
      • 8.8 Management of Technical Vulnerabilities
      • 8.9 Configuration Management
      • 8.10 Information Deletion
      • 8.11 Data masking
      • 8.12 Data leakage prevention
      • 8.13 Information backup
      • 8.14 Redundancy of information processing facilities
      • 8.15 Logging
      • 8.16 Monitoring activities
      • 8.17 Clock synchronization
      • 8.18 Use of privileged utility programs
      • 8.19 Installation of software on operational systems
      • 8.20 Networks security
      • 8.21 Security of Network Services
      • 8.22 Segregation of Networks
      • 8.23 Web filtering
      • 8.24 Use of Cryptography
      • 8.25 Secure Development Life Cycle
      • 8.26 Application Security Requirements
      • 8.27 Secure System Architecture & Engineering Principles
      • 8.28 Secure Coding
      • 8.29 Security Testing in Development and Acceptance
      • 8.30 Outsourced Development
      • 8.31 Separation of Development, Test, and Production Environments
      • 8.32 Change Management
      • 8.33 Test Information Security
      • 8.34 Protection of Information Systems During Audit Testing
      Obmondo

      Open-source platform for security, compliance, and operations — run on any cloud with no vendor lock-in.

      Products

      • Services
      • Features
      • Pricing
      • Compliance
      • Scope of Service

      Company

      • About
      • Solutions Brief
      • Careers
      • Blog
      • Why Obmondo

      Contact

      • info@obmondo.com
      • sales@obmondo.com
      • Talk to us
      • Contact Us

      © 2026 Obmondo. All rights reserved.

      Terms & ConditionsUnsubscribe
      1. compliance
      2. 8.27

      Secure System Architecture & Engineering Principles

      Principles for engineering secure systems should be established, documented, maintained and applied to any information system development activities.

      Design-first security approach

      Mermaid design diagrams are created before development. Risk assessments identify threats in data flow, access control, and technical constraints.

      Go/No-Go security checkpoints

      Security risk assessments determine whether a design is approved or must be stopped, this prevents flawed designs from entering development. If critical security issues are identified, development cannot proceed until all risks are remediated.

      Separate environments

      Development, staging, and production environments are completely isolated. Each has appropriate controls, access restrictions, and controlled deployment. This architectural separation prevents security incidents in one environment from impacting others.

      Zero Trust architecture and identity-based access

      Systems enforce authentication at every layer. Netbird provides identity-based network access, servers and cluster are secured using zero trust multi-factor authentication.

      On this page

      • Design-first security approach
      • Go/No-Go security checkpoints
      • Separate environments
      • Zero Trust architecture and identity-based access