Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Secure Communications
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Secure Communications concept in IT architecture decision-making refers to the implementation of measures that ensure the confidentiality, integrity, and availability of data transmitted between different systems or devices. This includes the use of encryption, digital signatures, and secure protocols such as SSL/TLS to protect data in transit from unauthorized access, interception, or modification. The Secure Communications concept is critical in ensuring the security of sensitive information such as financial transactions, personal data, and intellectual property. It is also essential for compliance with regulatory requirements such as HIPAA, PCI DSS, and GDPR.
Example: Secure Communications:
Decision: Enforcing Transport Layer Security (TLS) for secure communication over the network.
Rationale: TLS ensures that data transmitted between client and server is encrypted, preventing eavesdropping, tampering, and unauthorized interception of sensitive information.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/SecureCommunicationsGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:SecureCommunicationsGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947469
dct:title: Architecture Decision Record about Secure Communications
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
|
|
dct:modified | 2024-01-28 |
dct:identifier | ADR-20230515180947469 |
dct:title | Architecture Decision Record about Secure Communications |
skos:example | Secure Communications:
Decision: Enforcing Transport Layer Security (TLS) for secure communication over the network.
Rationale: TLS ensures that data transmitted between client and server is encrypted, preventing eavesdropping, tampering, and unauthorized interception of sensitive information. |
eira:adr_context | The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons. |
eira:adr_decision | The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how. |
eira:adr_status | [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)] |
eira:adr_consecuences | The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture. |
eira:concept | eira:ArchitectureBuildingBlock |
eira:definitionSource | ISO/IEC/IEEE 42010:2022 |
eira:definitionSourceReference | https://www.iso.org/standard/74393.html |
skos:note | The Secure Communications concept in IT architecture decision-making refers to the implementation of measures that ensure the confidentiality, integrity, and availability of data transmitted between different systems or devices. This includes the use of encryption, digital signatures, and secure protocols such as SSL/TLS to protect data in transit from unauthorized access, interception, or modification. The Secure Communications concept is critical in ensuring the security of sensitive information such as financial transactions, personal data, and intellectual property. It is also essential for compliance with regulatory requirements such as HIPAA, PCI DSS, and GDPR. |
eira:PURI | http://data.europa.eu/dr8/SecureCommunicationsGoal |
dct:type | eira:SecureCommunicationsGoal |
skos:definition | Architecture Decision Record from where you should specialise the ADR SBBs regarding the Secure Communications |
eira:view | Digital Solution Architecture Decisions Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal |