Functionally Interpreting Security.
Saved in:
| Title: | Functionally Interpreting Security. |
|---|---|
| Authors: | McEvilley, Michael (AUTHOR) mcevilley@mitre.org, Winstead, Mark (AUTHOR) mwinstead@mitre.org |
| Source: | Insight (2156-485X). Jun2022, Vol. 25 Issue 2, p15-18. 4p. |
| Subjects: | Work design, System safety, Systems engineering |
| Abstract: | The outcomes of an exploration of what security means as an engineered function are presented, based upon principles of secure system design. The exploration was done to support an effort to formalize the syntax and semantics for the expression of security protection needs in system requirements, and to enable alignments with system safety and resilience requirements. The exploration produced a clearer interpretation of the essential aspects of security as postulated by foundational work on secure system design and was cross checked against representative classes of security requirement criteria to confirm accuracy and sufficiency of coverage of key security requirement types. The resultant perspective of what it means to be secure can be useful to inform the development of effective practices for the design of secure systems that are aligned with Future of Systems Engineering (FuSE) concepts, particularly security as a functional requirement. Further, the perspective helps to distinguish those characteristics of security (loss of "anything") that are in common, and that contrast, with safety (loss of "specific things") and resilience (loss of "capability"). [ABSTRACT FROM AUTHOR] |
| Copyright of Insight (2156-485X) is the property of Wiley-Blackwell and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) | |
| Database: | Engineering Source |
| FullText | Text: Availability: 0 |
|---|---|
| Header | DbId: egs DbLabel: Engineering Source An: 157816221 AccessLevel: 6 PubType: Academic Journal PubTypeId: academicJournal PreciseRelevancyScore: 0 |
| IllustrationInfo | |
| Items | – Name: Title Label: Title Group: Ti Data: Functionally Interpreting Security. – Name: Author Label: Authors Group: Au Data: <searchLink fieldCode="AR" term="%22McEvilley%2C+Michael%22">McEvilley, Michael</searchLink> (AUTHOR)<i> mcevilley@mitre.org</i><br /><searchLink fieldCode="AR" term="%22Winstead%2C+Mark%22">Winstead, Mark</searchLink> (AUTHOR)<i> mwinstead@mitre.org</i> – Name: TitleSource Label: Source Group: Src Data: <searchLink fieldCode="JN" term="%22Insight+%282156-485X%29%22">Insight (2156-485X)</searchLink>. Jun2022, Vol. 25 Issue 2, p15-18. 4p. – Name: Subject Label: Subjects Group: Su Data: <searchLink fieldCode="DE" term="%22Work+design%22">Work design</searchLink><br /><searchLink fieldCode="DE" term="%22System+safety%22">System safety</searchLink><br /><searchLink fieldCode="DE" term="%22Systems+engineering%22">Systems engineering</searchLink> – Name: Abstract Label: Abstract Group: Ab Data: The outcomes of an exploration of what security means as an engineered function are presented, based upon principles of secure system design. The exploration was done to support an effort to formalize the syntax and semantics for the expression of security protection needs in system requirements, and to enable alignments with system safety and resilience requirements. The exploration produced a clearer interpretation of the essential aspects of security as postulated by foundational work on secure system design and was cross checked against representative classes of security requirement criteria to confirm accuracy and sufficiency of coverage of key security requirement types. The resultant perspective of what it means to be secure can be useful to inform the development of effective practices for the design of secure systems that are aligned with Future of Systems Engineering (FuSE) concepts, particularly security as a functional requirement. Further, the perspective helps to distinguish those characteristics of security (loss of "anything") that are in common, and that contrast, with safety (loss of "specific things") and resilience (loss of "capability"). [ABSTRACT FROM AUTHOR] – Name: AbstractSuppliedCopyright Label: Group: Ab Data: <i>Copyright of Insight (2156-485X) is the property of Wiley-Blackwell and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract.</i> (Copyright applies to all Abstracts.) |
| PLink | https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=157816221 |
| RecordInfo | BibRecord: BibEntity: Identifiers: – Type: doi Value: 10.1002/inst.12380 Languages: – Code: eng Text: English PhysicalDescription: Pagination: PageCount: 4 StartPage: 15 Subjects: – SubjectFull: Work design Type: general – SubjectFull: System safety Type: general – SubjectFull: Systems engineering Type: general Titles: – TitleFull: Functionally Interpreting Security. Type: main BibRelationships: HasContributorRelationships: – PersonEntity: Name: NameFull: McEvilley, Michael – PersonEntity: Name: NameFull: Winstead, Mark IsPartOfRelationships: – BibEntity: Dates: – D: 01 M: 06 Text: Jun2022 Type: published Y: 2022 Identifiers: – Type: issn-print Value: 2156485X Numbering: – Type: volume Value: 25 – Type: issue Value: 2 Titles: – TitleFull: Insight (2156-485X) Type: main |
| ResultId | 1 |
