Integrity represents the second core principle of software security, focused on ensuring data trustworthiness through accuracy and completeness.
Data Corruption Risks
The article notes that “data can be corrupted due to system errors, unauthorized modification, and data tampering.” These risks apply across all application types, regardless of domain.
Real-World Educational Platform Examples
In learning systems, integrity failures could result in graded submissions using outdated versions or incorrect grade assignments. The concept of eventual consistency acknowledges that distributed systems experience propagation delays—similar to inter-bank transfers requiring processing time.
Implementing Integrity Controls
The article identifies four key strategies:
Confidentiality Controls: Restricting edit access to assigned collaborators and limiting grading permissions to teachers prevents unauthorized alterations.
System Processing: Tracking workflow states ensures submissions remain locked during review and prevents teachers from grading unsubmitted work.
Error Handling: Failed notification systems should maintain submission locks and log failures rather than silently proceeding with inconsistent states.
Digital Signatures: Collaborative submissions with individual signatures provide proof of authorship and tamper evidence.
Non-Repudiation
The article emphasizes that high-integrity systems achieve non-repudiation—maintaining clear audit trails of user actions and data modifications. This capability proves essential for digital forensics and legal proceedings.