Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Retention and Data Deletion
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Retention and Data Deletion is a critical concept in IT architecture that deals with the management of data throughout its lifecycle. It involves the decision-making process of how long data should be kept, where it should be stored, and when it should be deleted. The concept is essential for organizations to comply with legal and regulatory requirements, protect sensitive information, and optimize storage resources. The retention and data deletion policy should be well-defined, communicated, and enforced to ensure data is managed effectively and efficiently. The policy should also consider the potential risks associated with data breaches, data loss, and unauthorized access.
Example: Retention and Data Deletion:
Decision: Implementing data retention policies and mechanisms for secure data deletion when no longer required.
Rationale: Data retention and deletion policies ensure compliance with regulations governing the storage and retention of data, minimizing the risk of unauthorized access to obsolete or unnecessary data.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/RetentionAndDataDeletionGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:RetentionAndDataDeletionGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947804
dct:title: Architecture Decision Record about Retention and Data Deletion
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-20230515180947804 |
dct:title | Architecture Decision Record about Retention and Data Deletion |
skos:example | Retention and Data Deletion:
Decision: Implementing data retention policies and mechanisms for secure data deletion when no longer required.
Rationale: Data retention and deletion policies ensure compliance with regulations governing the storage and retention of data, minimizing the risk of unauthorized access to obsolete or unnecessary data. |
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 | Retention and Data Deletion is a critical concept in IT architecture that deals with the management of data throughout its lifecycle. It involves the decision-making process of how long data should be kept, where it should be stored, and when it should be deleted. The concept is essential for organizations to comply with legal and regulatory requirements, protect sensitive information, and optimize storage resources. The retention and data deletion policy should be well-defined, communicated, and enforced to ensure data is managed effectively and efficiently. The policy should also consider the potential risks associated with data breaches, data loss, and unauthorized access. |
eira:PURI | http://data.europa.eu/dr8/RetentionAndDataDeletionGoal |
dct:type | eira:RetentionAndDataDeletionGoal |
skos:definition | Architecture Decision Record from where you should specialise the ADR SBBs regarding the Retention and Data Deletion |
eira:view | Digital Solution Architecture Decisions Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal |