How Systems Security Engineering Unifies Technology, Security, and Mission Outcomes
A practical technical reference for the people who specify, engineer, acquire, assess, operate and lead complex systems.
A system can satisfy its security controls and still fail its mission when assumptions about interfaces, authority, dependencies or operating conditions prove wrong.
The Security-Engineering Convergence examines Systems Security Engineering (SSE) as the security specialty integrated within systems engineering. It does not present SSE as a replacement for systems engineering, cybersecurity operations, risk management or compliance. Instead, it shows how those contributions can connect to the engineering work that shapes system behaviour across its life cycle.
The book follows a practical line of reasoning: establish the needed mission outcome, characterize the system and its context, investigate adversity and loss, develop requirements, choose and assess architectures, evaluate evidence, and maintain the resulting basis for trust through acquisition, operation, change and retirement.
Integrate protection needs, security-specific analyses and assurance into established engineering decisions and artefacts.
Connect controls, threat analysis, assessments and operations to requirements, architecture, verification and mission consequence.
Understand what to demand from suppliers, what evidence means, and where decision authority and residual uncertainty remain.
The material progresses from shared foundations through requirements, architecture, implementation, assurance, operational sustainment and emerging system challenges. This chapter list reflects the current published Edition 1.1.
The relationship among mission capability, the system boundary, controls, risk and integrated engineering responsibilities.
Develop protection needs, analyze adversity, allocate requirements and plan the evidence required to justify claims.
Reason about architecture, composed systems, models, design alternatives and controlled degradation.
Connect production and enabling systems to integration, verification, validation, human use and transition.
Specify supplier obligations, examine assurance arguments and support accountable acceptance decisions.
Carry the engineering baseline into operation, maintenance, cloud dependencies, legacy systems and retirement.
Integrate technical management, competence, systems-of-systems and human–AI engineering.
Worked and bounded cases, modelling orientation, information-flow analysis, resilience under supplier compromise, and reusable worksheets complement the chapters.
Edition 1.1 adds engineering-focused treatment of privacy and adaptation under adverse conditions, improves explanation around the technical figures, and includes standards-oriented crosswalks in the companion resources.
The earlier Edition 1.0 remains available for readers using or citing that version. The editions have separate version-specific Zenodo DOIs.
The book uses scenarios and case records to demonstrate engineering reasoning rather than merely describe successful outcomes. It distinguishes hypothetical case assumptions, analytical models, executed teaching-code tests, technical evidence and the decisions that evidence may—or may not—support.
Mission needs, losses, requirements, architectures, evaluations and decisions remain connected.
Worked material includes administrative authority, cyber-physical motion, information flow and trusted-source compromise.
Worksheets support documenting protection needs, allocation, architectural trade-offs, evidence applicability and change impact.
Illustrative case material must not be mistaken for evidence that a corresponding real-world operational system has been tested, authorized or validated.
Download the current Edition 1.1 and companion materials. The paginated PDF is the authoritative reference edition; the reflowable EPUB is an alternative for compatible reading applications.
Complete paginated reference with chapters, figures, tables and appendices.
Reflowable reading version. Complex technical layouts may be more reliable in the PDF.
Teaching model, worked examples, diagrams, worksheets and the new standards crosswalks.
Check the release notes and SHA-256 checksums for edition changes and file integrity. No illustrative example constitutes verification of an actual deployed system.
Except where otherwise expressly indicated, material for which the author holds the necessary rights is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0) ↗. Separately identified third-party materials retain their applicable terms.
Hillier, P. J. (2026). The Security-Engineering Convergence: How Systems Security Engineering Unifies Technology, Security, and Mission Outcomes (Edition 1.1). Hillier Information Protection Solutions Inc. https://doi.org/10.5281/zenodo.23338555.
Earlier Edition 1.0: https://doi.org/10.5281/zenodo.23284495
For reproducibility and citations, the original published edition remains available: GitHub v1.0.0 downloads ↗ and Zenodo Edition 1.0 ↗.
Each published edition has its own Zenodo DOI. Earlier files remain available rather than being silently replaced. Cite the version you actually used.
This work is independently authored. It should not be mistaken for an official defence, government or standards-body publication.