0% found this document useful (0 votes)
9 views3 pages

Preventing Data Diddling in Systems

The document discusses the issue of data diddling, which is the unauthorized manipulation of data that can lead to inaccuracies and fraud, particularly in sensitive sectors. It outlines a project aimed at developing a system to detect and prevent such manipulations through user authentication, input validation, and audit trails. The proposed system has merits such as enhanced data integrity and early detection of issues, but also faces challenges like increased complexity and resource demands.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views3 pages

Preventing Data Diddling in Systems

The document discusses the issue of data diddling, which is the unauthorized manipulation of data that can lead to inaccuracies and fraud, particularly in sensitive sectors. It outlines a project aimed at developing a system to detect and prevent such manipulations through user authentication, input validation, and audit trails. The proposed system has merits such as enhanced data integrity and early detection of issues, but also faces challenges like increased complexity and resource demands.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

1.

Problem Identification
Data Diddling refers to the unauthorized alteration or manipulation of data, typically during
data entry or transmission, which can lead to incorrect, fraudulent, or misleading information
in a system.

In many organizations, especially those dealing with financial, medical, or personal data, data
diddling poses a major threat. The problem is that data can be tampered with before it is
processed or saved into the system, leading to inaccurate records, fraud, or wrong decisions.

2. Statement of Intent
The intent of this project is to develop a system that detects and prevents data diddling during
data entry or transmission. The project aims to:

 Identify points where data manipulation is likely to occur.


 Implement validation and verification mechanisms to ensure data integrity.
 Alert administrators or users when suspicious data changes are detected.
 Provide audit trails to track data modifications.

3. Main Idea / Theme / Topic


Theme: Data Integrity and Security
Topic: Detection and Prevention of Data Diddling in Information Systems

The project focuses on enhancing the reliability of data in computer systems by preventing
unauthorized or accidental data manipulation.

4. Design Specifications
Functional Requirements

 User Authentication: Only authorized users can input or modify data.


 Input Validation: Ensure data conforms to expected formats and ranges.
 Data Encryption: Secure data transmission to prevent interception and alteration.
 Audit Logging: Record all data entries and changes with timestamps and user info.
 Data Comparison: Detect discrepancies between original and modified data.
 Alert System: Notify relevant parties when data inconsistency or suspicious behavior
is detected.
Non-functional Requirements

 Usability: Simple and user-friendly interface for data entry and monitoring.
 Security: Use of encryption and access control.
 Performance: Minimal delay in data processing and validation.
 Reliability: Accurate detection of data diddling attempts without false alarms.
 Scalability: Should handle increasing amounts of data and users.

5. Evaluation of Already Existing Ideas


Several approaches exist to address data diddling:

a) Input Validation and Access Control

 Merits: Simple to implement; prevents common errors and unauthorized access.


 Demerits: Does not prevent intentional data manipulation by authorized users.

b) Cryptographic Techniques (Hashing, Digital Signatures)

 Merits: Ensures data integrity; any alteration can be detected.


 Demerits: Requires more computational resources; complex implementation.

c) Audit Trails and Logging

 Merits: Provides traceability; can identify who changed data and when.
 Demerits: Does not prevent data diddling, only detects it after the fact.

d) Blockchain-based Solutions

 Merits: Tamper-proof record keeping; high data integrity.


 Demerits: High complexity; resource-intensive; may not suit all applications.

6. Merits and Demerits of the Proposed


System
Merits

 Provides multiple layers of protection against data manipulation.


 Enables early detection of data diddling attempts.
 Maintains detailed logs for accountability.
 Enhances trust in the data within the system.
Demerits

 Increased system complexity may require more training for users.


 Additional resource requirements for encryption and logging.
 Potential delays in data processing due to validation and monitoring.
 Cannot fully prevent data diddling by highly skilled insiders with access

You might also like