Test deck2 Flashcards
ISO 15288:2015
systems engineering standard covering processes and life cycle stages.
ISO 15288:2015 processes that are divide into four categories
- Agreement 2. Organization project-enabling 3. Technical Management 4. Technical
The left side of the V (V-Model) represents
concept development and the decomposition of requirements into functions and physical entities that can be architected, designed, and developed.
The right side of the V represents
integegration of these entities and their ultimate transition into the field, where they are operated and maintained.
Defense in Depth
The use of overlapping layers of controls/countermeasures to create a series of defensive layers of physical, administrative, technical types to secure assets.
Common Criteria (ISO 15408)
Provides a structure methodology for documenting security requirements, documenting and validating security capabilities, and promoting international cooperation in the are of IT security. Use of the common criteria “protection profiles” and “security targets” greatly aids in the development of products and systems that have IT security functions.
What is ISO/IEC 21827:2008
System Security Engineering - capability Maturity Model (SSE-CMM), describes the essential characteristics of an organization’s security engineering process that must exist to ensure good security engineering. It does NOT prescribe a particular process or sequence, but captures practices generally observed in industry.
ISO 21827 covers the following standard security metric for security engineering practices
- The entire life cycle, including development, operation, maintenance, and decommission activities. (DOM, D) 2. The whole organization, including management, organizational, and engineering activities. 3. Concurrent interactions with other disciplines, such as system, software, hardware, human factors, test engineering, system management, operation, and maintenance. 4. Interactions with other organizations, including acquisition, system management, certification, accreditation, and evaluation.
Subjects Objects
Users Data
Closed Open Systems
Vendor Specific Industry Standard
Confinement (sandboxing)
Ability to control read/write activity as software executes in a system and accesses memory
Bounds
limits set on the memory addresses and resources a process can access in a system
Isolation
the ability to use bounds and confinement to control the impact process behavior has on a system
Controls (in the context of access)
use of access rules to limit subject / object interaction