MLchartDataset catalogue

Architecture

Term · Cybersecurity · MLC-T-CYB-000204

1. A highly structured specification of an acceptable approach within a framework for solving a specific problem. An architecture contains descriptions of all the components of a selected, acceptable solution while allowing certain details of specific components to be variable to satisfy related constraints (e.g., costs, local environment, user acceptability).

2. Fundamental concepts or properties related to a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.

3. A set of physical and logical security-relevant representations (i.e., views) of system architecture that conveys information about how the system is partitioned into security domains and makes use of security-relevant elements to enforce security policies within and between security domains based on how data and information must be protected.

4. A set of physical and logical security-relevant representations (i.e., views) of system architecture that conveys information about how the system is partitioned into security domains and makes use of security-relevant elements to enforce security policies within and between security domains based on how data and information must be protected. Note: The security architecture reflects security domains, the placement of security-relevant elements within the security domains, the interconnections and trust relationships between the security-relevant elements, and the behavior and interaction between the security-relevant elements. The security architecture, similar to the system architecture, may be expressed at different levels of abstraction and with different scopes.

5. An embedded, integral part of the enterprise architecture that describes the structure and behavior for an enterprise’s security processes, information security systems, personnel and organizational sub-units, showing their alignment with the enterprise’s mission and strategic plans. See information security architecture.

6. A highly structured specification of an acceptable approach within a framework for solving a specific problem. An architecture contains descriptions of all the components of a selected, acceptable solution, while allowing certain details of specific components to be variable to satisfy related constraints (e.g., costs, local environment, user acceptability).

7. The design of the network of the hotel environment and the components that are used to construct it.

8. the design of the network of the hotel environment and the components that are used to construct it

9. complying with the principles that drive the system design; i.e., guidelines on the placement and implementation of specific security services within various distributed computing environments.

10. Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.

11. A set of related physical and logical representations (i.e., views) of a system or a solution. The architecture conveys information about system/solution elements, interconnections, relationships, and behavior at different levels of abstractions and with different scopes.
Refer to security architecture.

12. A set of physical and logical security-relevant representations (i.e., views) of system architecture that conveys information about how the system is partitioned into security domains and makes use of security-relevant elements to enforce security policies within and between security domains based on how data and information must be protected.
Note: The security architecture reflects security domains, the placement of security-relevant elements within the security domains, the interconnections and trust relationships between the security-relevant elements, and the behavior and interactions between the security-relevant elements. The security architecture, similar to the system architecture, may be expressed at different levels of abstraction and with different scopes.

Table 1. Record
IdentifierMLC-T-CYB-000204
FieldCybersecurity
Synonymssecurity architecture
ReferencesFIPS 201-3; NIST SP 1800-25B from FIPS 201-2; FIPS 201 [version unknown]; NIST SP 1800-10B from FIPS 201-2; NIST SP 800-160v1r1 from ISO/IEC/IEEE 42010:2011; NIST SP 800-160v1r1; NIST SP 800-37 Rev. 2 from NIST SP 800-160 Vol. 1; NIST SP 800-37 Rev. 2 from NIST SP 800-39; NIST SP 1800-26B from FIPS 201-2; NIST SP 1800-27B; NIST SP 1800-27C; NIST SP 800-27 Rev. A [Withdrawn]; NIST SP 800-160 Vol. 1 from ISO/IEC/IEEE 42010; NIST SP 800-160v1r1 from ISO/IEC/IEEE 42010:2011; NIST SP 800-160 Vol. 1; NIST CSRC Glossary
See alsoSecurity architecture
Record as JSON
{
  "id": "MLC-T-CYB-000204",
  "term": "Architecture",
  "field": "Cybersecurity",
  "definition": "1. A highly structured specification of an acceptable approach within a framework for solving a specific problem. An architecture contains descriptions of all the components of a selected, acceptable solution while allowing certain details of specific components to be variable to satisfy related constraints (e.g., costs, local environment, user acceptability).\n\n2. Fundamental concepts or properties related to a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.\n\n3. A set of physical and logical security-relevant representations (i.e., views) of system architecture that conveys information about how the system is partitioned into security domains and makes use of security-relevant elements to enforce security policies within and between security domains based on how data and information must be protected.\n\n4. A set of physical and logical security-relevant representations (i.e., views) of system architecture that conveys information about how the system is partitioned into security domains and makes use of security-relevant elements to enforce security policies within and between security domains based on how data and information must be protected. Note: The security architecture reflects security domains, the placement of security-relevant elements within the security domains, the interconnections and trust relationships between the security-relevant elements, and the behavior and interaction between the security-relevant elements. The security architecture, similar to the system architecture, may be expressed at different levels of abstraction and with different scopes.\n\n5. An embedded, integral part of the enterprise architecture that describes the structure and behavior for an enterprise’s security processes, information security systems, personnel and organizational sub-units, showing their alignment with the enterprise’s mission and strategic plans. See information security architecture.\n\n6. A highly structured specification of an acceptable approach within a framework for solving a specific problem. An architecture contains descriptions of all the components of a selected, acceptable solution, while allowing certain details of specific components to be variable to satisfy related constraints (e.g., costs, local environment, user acceptability).\n\n7. The design of the network of the hotel environment and the components that are used to construct it.\n\n8. the design of the network of the hotel environment and the components that are used to construct it\n\n9. complying with the principles that drive the system design; i.e., guidelines on the placement and implementation of specific security services within various distributed computing environments.\n\n10. Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.\n\n11. A set of related physical and logical representations (i.e., views) of a system or a solution. The architecture conveys information about system/solution elements, interconnections, relationships, and behavior at different levels of abstractions and with different scopes.\nRefer to security architecture.\n\n12. A set of physical and logical security-relevant representations (i.e., views) of system architecture that conveys information about how the system is partitioned into security domains and makes use of security-relevant elements to enforce security policies within and between security domains based on how data and information must be protected.\nNote: The security architecture reflects security domains, the placement of security-relevant elements within the security domains, the interconnections and trust relationships between the security-relevant elements, and the behavior and interactions between the security-relevant elements. The security architecture, similar to the system architecture, may be expressed at different levels of abstraction and with different scopes.",
  "synonyms": [
    "security architecture"
  ],
  "see_also": [
    "security architecture"
  ],
  "references": [
    "FIPS 201-3; NIST SP 1800-25B from FIPS 201-2; FIPS 201 [version unknown]; NIST SP 1800-10B from FIPS 201-2",
    "NIST SP 800-160v1r1 from ISO/IEC/IEEE 42010:2011",
    "NIST SP 800-160v1r1",
    "NIST SP 800-37 Rev. 2 from NIST SP 800-160 Vol. 1",
    "NIST SP 800-37 Rev. 2 from NIST SP 800-39",
    "NIST SP 1800-26B from FIPS 201-2",
    "NIST SP 1800-27B",
    "NIST SP 1800-27C",
    "NIST SP 800-27 Rev. A [Withdrawn]",
    "NIST SP 800-160 Vol. 1 from ISO/IEC/IEEE 42010; NIST SP 800-160v1r1 from ISO/IEC/IEEE 42010:2011",
    "NIST SP 800-160 Vol. 1",
    "NIST CSRC Glossary"
  ],
  "url": "https://mlchart.com/terminology/cybersecurity/architecture/"
}

Record 203 of 4,669 in Cybersecurity terminology (MLC-0102). Request the full dataset.