{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,2,21]],"date-time":"2025-02-21T20:17:44Z","timestamp":1740169064607,"version":"3.37.3"},"reference-count":45,"publisher":"Institute of Electrical and Electronics Engineers (IEEE)","license":[{"start":{"date-parts":[[2017,1,1]],"date-time":"2017-01-01T00:00:00Z","timestamp":1483228800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/creativecommons.org\/licenses\/by\/3.0\/legalcode"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":["IEEE Access"],"published-print":{"date-parts":[[2017]]},"DOI":"10.1109\/access.2017.2670781","type":"journal-article","created":{"date-parts":[[2017,3,10]],"date-time":"2017-03-10T07:40:21Z","timestamp":1489131621000},"page":"3465-3474","source":"Crossref","is-referenced-by-count":5,"title":["System-Agnostic Security Domains for Understanding and Prioritizing Systems Security Engineering Efforts"],"prefix":"10.1109","volume":"5","author":[{"given":"Stephen","family":"Khou","sequence":"first","affiliation":[],"role":[{"role":"author","vocabulary":"crossref"}]},{"ORCID":"https:\/\/orcid.org\/0000-0002-7034-8083","authenticated-orcid":false,"given":"Logan O.","family":"Mailloux","sequence":"additional","affiliation":[],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"John M.","family":"Pecarina","sequence":"additional","affiliation":[],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"263","reference":[{"key":"ref39","doi-asserted-by":"publisher","DOI":"10.1002\/inst.201114232"},{"key":"ref38","doi-asserted-by":"publisher","DOI":"10.1002\/sys.21211"},{"journal-title":"Framework for SCADA security policy","year":"2005","author":"kilman","key":"ref33"},{"journal-title":"NIST SP 800-53 Revision 4 Security and Privacy Controls for Federal Information Systems and Organizations","year":"2013","key":"ref32"},{"article-title":"Operating system security and secure operat-ing systems","year":"2003","author":"yang","key":"ref31"},{"year":"2014","author":"inserra","key":"ref30"},{"article-title":"System security engineering for program protection and cybersecurity","year":"0","author":"reed","key":"ref37"},{"journal-title":"Mandiant APTI Exposing One of China's Cyber Espionage Units","year":"2013","key":"ref36"},{"journal-title":"Report on Rules of System Composition Principles of Secure System Design","year":"1993","author":"boudra","key":"ref35"},{"key":"ref34","doi-asserted-by":"publisher","DOI":"10.21236\/AD0772806"},{"article-title":"NIST SP 800-14 generally accepted principles and practices for security information technology systems","year":"1996","author":"swanson","key":"ref10"},{"journal-title":"Resilient Military Systems and the Advanced Cyber Threat","year":"2013","key":"ref40"},{"journal-title":"Information Technology Security Evaluation Criteria","year":"1991","key":"ref11"},{"journal-title":"Canadian Trusted Computer Product Evaluation Criteria","year":"1993","key":"ref12"},{"journal-title":"ISO\/IEC 15408&#x2014;Information Technology&#x2014;Security Techniques&#x2014;Evaluation Criteria for IT Security","year":"1999","key":"ref13"},{"article-title":"NIST SP 800-160 systems security engineering: Considerations for a multidisciplinary approach in the engineering of trustworthy secure systems","year":"2016","author":"ross","key":"ref14"},{"journal-title":"Defense Acquisition Guidebook","year":"2010","key":"ref15"},{"journal-title":"Security Engineering","year":"2015","key":"ref16"},{"key":"ref17","article-title":"Security risk analysis for complex systems","author":"branagan","year":"2006","journal-title":"Information Systems Security Association Journal"},{"journal-title":"Security Engineering","year":"2008","author":"anderson","key":"ref18"},{"journal-title":"Official (ISC)2 Guide to the CISSP CBK","year":"2015","author":"tipton","key":"ref19"},{"journal-title":"Systems Engineering Guide","year":"2014","key":"ref28"},{"journal-title":"Dept of Defense Standard 5200 28 Trusted Computer System Evaluation Criteria","year":"1983","key":"ref4"},{"journal-title":"Engineering for System Assurance","year":"2008","key":"ref27"},{"journal-title":"Security Patterns Integrating Security and Systems Engineering","year":"2006","author":"schumacher","key":"ref3"},{"journal-title":"Security controls for computer systems","year":"1970","key":"ref6"},{"journal-title":"Engineering for System Assurance in NATO Programmes","year":"2010","key":"ref29"},{"key":"ref5","doi-asserted-by":"publisher","DOI":"10.1002\/inst.12092"},{"journal-title":"Principled Assuredly Trustworthy Composable Architectures","year":"2004","author":"neumann","key":"ref8"},{"journal-title":"Military Handbook 1785 System Security Engineering Program Management Requirements","year":"1989","key":"ref7"},{"key":"ref2","doi-asserted-by":"publisher","DOI":"10.1109\/MSP.2016.77"},{"journal-title":"Generally Accepted Information Security Principles","year":"2004","key":"ref9"},{"key":"ref1","doi-asserted-by":"publisher","DOI":"10.1109\/SysCon.2012.6189463"},{"journal-title":"ISO\/IEC 27002 Information Technology&#x2014;Security Techniques&#x2014;Code of Practice for Information Security Management","year":"2013","key":"ref20"},{"key":"ref45","doi-asserted-by":"publisher","DOI":"10.1109\/SysCon.2013.6549907"},{"journal-title":"Minimum Security Requirements for Federal Information and Information Systems","year":"2006","key":"ref22"},{"journal-title":"45 CFR 95 621&#x2014;ADP Reviews","year":"1990","key":"ref21"},{"key":"ref42","doi-asserted-by":"publisher","DOI":"10.1109\/MSP.2014.81"},{"journal-title":"Catalog of Control Systems Security Recommendations for Standards Developers","year":"2011","key":"ref24"},{"journal-title":"Cyber Resiliency Engineering Framework","year":"2011","author":"bodeau","key":"ref41"},{"journal-title":"Transportation Systems Sector-Specific Plan An Annex to the National Infrastructure Protection","year":"2010","key":"ref23"},{"journal-title":"ISO\/IEC 21827 Information Technology&#x2014;Security Techniques&#x2014;Systems Security Engineering&#x2014;Capability Maturity Model (SSE-CMM)","year":"2008","key":"ref44"},{"key":"ref26","first-page":"13","article-title":"Usable security: Why do we need it? How do we get it?","author":"sasse","year":"2005","journal-title":"Proc Security Usability Designing Secure Syst Sebastopol O&#x2019;Reilly"},{"key":"ref43","doi-asserted-by":"publisher","DOI":"10.1109\/MSP.2010.123"},{"key":"ref25","doi-asserted-by":"publisher","DOI":"10.1145\/1592761.1592773"}],"container-title":["IEEE Access"],"original-title":[],"link":[{"URL":"http:\/\/xplorestaging.ieee.org\/ielx7\/6287639\/7859429\/07875118.pdf?arnumber=7875118","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2022,1,12]],"date-time":"2022-01-12T16:26:11Z","timestamp":1642004771000},"score":1,"resource":{"primary":{"URL":"https:\/\/ieeexplore.ieee.org\/document\/7875118\/"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2017]]},"references-count":45,"URL":"https:\/\/doi.org\/10.1109\/access.2017.2670781","relation":{},"ISSN":["2169-3536"],"issn-type":[{"type":"electronic","value":"2169-3536"}],"subject":[],"published":{"date-parts":[[2017]]}}}