Secure File Storage Using Hybrid Cryptography: A Comprehensive Overview

Introduction

The project Secure File Storage using Hybrid Cryptography addresses modern data‑security challenges by combining multiple encryption algorithms with steganography. Implemented in Java with JSP/JavaScript front‑end and MySQL back‑end, it offers confidential storage, controlled sharing, and robust integrity verification.

Why a New System Is Needed

• Single‑layer encryption is insufficient – modern attackers can break AES‑only or DES‑only schemes.
• Data must be protected during storage, transmission, and sharing – users often need to send files to others, exposing them to interception.
• Key management and integrity checks are weak in conventional solutions.

Existing System Overview

• Uses a single encryption algorithm (often AES or DES) for each file.
• Access control relies on basic permission checks.
• Provides only basic admin monitoring and no advanced sharing or integrity verification.
• Limitations include single‑layer protection, centralized key management, limited sharing features, minimal integrity checks, and scalability concerns.

Proposed System Architecture

1. User Layer – registration, login, file upload/download.
2. File Processing Layer –
3. Split each uploaded file into three blocks.
4. Apply triple encryption (AES, TripleDES, Blowfish) to each block.
5. Embed the decryption key into an image using LSB‑based steganography.
6. Control Sharing Layer – encrypted files can be shared only with authorized users who possess the correct stego‑image.
7. Recovery Layer – verifies block integrity, reconstructs the original file after successful key extraction.
8. Secure Storage – encrypted blocks and stego images are stored on the server (E:\SecureVault folder).

Encryption & Steganography Details

• Triple Encryption – each block passes through AES → TripleDES → Blowfish, providing layered security.
• LSB Steganography – the secret key is hidden in the least‑significant bits of a carrier image (referred to as the signo image). Without this exact image, decryption fails.
• Block Splitting – prevents attackers from reconstructing the file even if they obtain some blocks.

User Workflow

• Registration & Login – users create accounts (e.g., JP, Ajit, Vijay).
• Upload – select a file (PDF, DOC, TXT), provide a secret key, choose a carrier image, and click Encrypt & Upload.
• File Storage – the system creates three encrypted parts and a stego image stored in the secure vault.
• Sharing – the owner selects recipients; the system records a pending share request.
• Acceptance – the recipient logs in, views pending shares, and accepts.
• Decryption – the recipient downloads the stego image, uploads it in the Verify & Decrypt module, and the system reconstructs the original file after integrity checks.
• Error Handling – using an incorrect stego image results in an error, preventing unauthorized access.

Administrative Dashboard

• Analytics Overview – total users, encrypted files, shares, downloads, file sizes, and trends over the last six months.
• User Management – view registration details, edit or delete users.
• File Statistics – per‑user file counts, sizes, and activity.
• Sharing & Download Reports – status of shares (pending, accepted, declined) and download sources with IP logs.
• Reports – visual charts comparing activity, radar charts for operation balance, and monthly summaries.

Implementation Details

• Programming Language: Java (JDK 23.0.1)
• Front‑End: JSP, CSS, JavaScript
• IDE: Apache NetBeans 24
• Server: Apache Tomcat 9.0.84
• Database: MySQL 8.0 (schema secure_vault)
• Hardware: Standard PC with Windows 10/11, E: drive for file storage.

Frequently Asked Questions (FAQs)

• Purpose: Provide a highly secure platform for storing, sharing, and retrieving files using hybrid cryptography and steganography.
• Technologies Used: Java, JSP, CSS, JavaScript, MySQL.
• Hybrid Cryptography Definition: Combination of multiple encryption algorithms (AES, TripleDES, Blowfish) to strengthen security.
• Key Protection: Keys are hidden inside an image via LSB steganography.
• Sharing Mechanism: Files are shared encrypted; recipients must be authenticated and supply the correct stego image to decrypt.
• Access Without Stego Image: Not possible; decryption fails.
• Incorrect Image Handling: System returns an error and does not extract the file.
• Data Integrity: Verified during recovery by checking each block before reconstruction.
• Admin Features: User details, file statistics, sharing/download analytics, activity logs.
• Scalability: Modular Java‑MySQL architecture supports growth in users and files.
• Supported File Types: Documents, images, text files (PDF, DOC, TXT, etc.).
• Activity Logging: Detailed logs for uploads, downloads, and sharing are available to admins.

Conclusion

• Layered encryption dramatically raises the barrier for attackers.
• Embedding keys in images eliminates the need for separate key distribution channels.
• Controlled sharing ensures only authorized recipients can access files.
• Comprehensive admin analytics provide visibility and auditability.

• **The modular Java‑MySQL stack enables easy scaling for larger deployments.

• Multi‑layer encryption (AES, TripleDES, Blowfish) provides robust protection against modern attacks.

• LSB steganography secures decryption keys within carrier images, preventing key leakage.
• Controlled sharing with mandatory stego‑image verification ensures only intended recipients can decrypt files.
• Detailed administrative analytics and logging give full visibility into user activity and system health.
• The Java‑based modular architecture allows the solution to scale efficiently as user and file volumes grow.