ATLOCK v4 described as layered Windows desktop security suite with detection and lockdown

"I didn't want to build another password locker. I wanted to build something that reacts to attacks." Most desktop security applications follow a simple pattern. Password ↓ Unlocked I wanted something different. Authentication ↓ Detection ↓ Evidence Collection ↓ Notification ↓ Escalation ↓ Lockdown That idea eventually became ATLOCK v4. 🚀 The Goal Instead of protecting one thing, I wanted multiple security layers working together. The final system combines: ✅ File Protection ✅ Password Vault ✅ Intruder Detection ✅ Camera Evidence ✅ Windows Lockdown ✅ Notification Engine All inside one desktop application. 🏗 System Architecture ATLOCK v4 ┌──────────────────────────┐ │ Lockdown Engine │ └─────────────┬────────────┘ │ ┌─────────────────┼─────────────────┐ ▼ ▼ ▼ File Guard Password Vault Intruder Engine │ │ │ NTFS ACL Fernet Crypto OpenCV Camera │ │ │ └─────────────────┼─────────────────┘ ▼ Notification Manager Every module has exactly one responsibility. That made debugging much easier than maintaining a single massive file. 🔐 Challenge #1 Passwords Should Never Be Stored The first design decision was simple. Passwords should never exist as plain text. Pipeline: Master Password ↓ PBKDF2-HMAC-SHA256 ↓ 200,000 Iterations ↓ Derived Key ↓ Fernet Encryption ↓ Encrypted Vault Why? Because even if someone steals the encrypted vault, they still can't read its contents without the correct key. 🛡 Challenge #2 File Protection Many "file lockers" rename files hide folders change icons That isn't real protection. Instead, ATLOCK works directly with Windows. Application ↓ Windows Security ↓ NTFS Access Control Lists ↓ Access Denied When ACLs aren't available, the application gracefully switches to an alternative protection method. 📸 Challenge #3 Turning Failed Passwords into Security Events Instead of Wrong Password ↓ Try Again I built Wrong Password ↓ Capture Photo ↓ Send Notification ↓ More Attempts ↓ Record Video ↓ Alarm ↓ System Lockdown Authentication became an event pipeline instead of a boolean check. ⚙ Challenge #4 Keeping the UI Responsive Running camera encryption monitoring alarms on the main thread would freeze the interface. So I separated long-running operations into background workers. UI Thread │ ├── Camera Thread ├── Alarm Thread ├── Notification Thread └── Monitoring Thread The application remains responsive while security operations continue independently. 🔔 Challenge #5 Logging Without Leaking Information One mistake many applications make is storing sensitive logs. ATLOCK never records plaintext passwords. Instead it stores Attempt ↓ Timestamp ↓ Masked Password ↓ Photo ↓ Video ↓ Result Example ********** (10 chars) instead of SuperSecret123 Even logs should follow the principle of least exposure. 🧩 Design Philosophy Rather than asking "Can I stop every attacker?" I asked "Can I make every attack visible?" That completely changed the architecture. Security became Detect ↓ Record ↓ Respond ↓ Recover instead of Accept ↓ Reject 🛠 Tech Stack Python ↓ PyQt ↓ OpenCV ↓ Cryptography ↓ Windows API ↓ NTFS ACL ↓ Threading ↓ JSON Configuration Each technology solved one specific problem. 📊 Lessons Learned Building ATLOCK v4 taught me: ✔ Security isn't one feature. ✔ Cryptography alone isn't enough. ✔ UX matters in security software. ✔ Modular architecture scales better. ✔ Logging is part of security. ✔ Defensive programming saves hours of debugging. 🚀 What's Next The roadmap includes: Hardware security key support Secure cloud synchronization Plugin system Argon2-based key derivation Cross-platform backend Signed updates Final Thoughts ATLOCK v4 isn't trying to replace enterprise endpoint security or antivirus software. Its goal is different: explore how multiple independent security layers—cryptography, operating system features, event-driven detection, and forensic logging—can work together inside a desktop application. That journey taught me far more about software engineering than simply building another password manager ever could. ATLOCK v4 has been one of the most challenging and rewarding projects I've built, pushing me to learn Windows APIs, applied cryptography, concurrency, and defensive software design. 🔗ATLOCK on GitHub: https://github.com/Akhouri-Anmol-Kumar/ATLOCK 🔗Direct Download(ATLOCK): https://github.com/Akhouri-Anmol-Kumar/ATLOCK/releases/download/v4.0/ATLOCK.zip ATLOCK is built by Akhouri Anmol Kumar Under Akhouri Systems ATLOCK is akhouri systems flagship product but we have built more 3 apps. Try Them Too! to be the part of the akhouri systems ecosystem APIC(image edition tool)-https://github.com/Akhouri-Anmol-Kumar/APIC ACALCU v3(world's most customizable calculator)-https://github.com/Akhouri-Anmol-Kumar/ACALCU-v3 ANOTE(a premium text editor with many features---The notepad killer)- https://github.com/Akhouri-Anmol-Kumar/ANOTE "We Build What others Forgot To Fix"

Most "file lockers" are just password gates. I wanted something different. Something that combines OS-level security, cryptography, intrusion detection, forensic logging and system lockdown into one desktop application. ⚡ What is ATLOCK v4? ATLOCK v4 is a Python-based Windows security suite designed around a simple philosophy: Security shouldn't stop after asking for a password. Instead, every failed authentication becomes an event that triggers multiple independent security layers. Wrong Password │ ▼ Intruder Detection │ ┌─────┴────────┐ │ │ Photo Video │ │ ▼ ▼ Notifications Logging │ ▼ Security Escalation 🧩 Architecture ATLOCK v4 ┌────────────────────────────┐ │ Lockdown Engine │ └────────────┬───────────────┘ │ ┌──────────────┼──────────────┐ ▼ ▼ ▼ File Guard Password Vault Intruder Ops │ │ │ NTFS ACL Fernet AES Camera Engine │ │ │ └──────────────┼──────────────┘ ▼ Notification Engine Instead of making one giant security module, every subsystem is isolated. That means: easier debugging easier upgrades less coupling independent security layers 🔐 1. Real Cryptography (No XOR Tricks) One thing I wanted to eliminate completely was fake encryption. Many hobby projects still rely on: XOR Caesar shifts Base64 homemade encryption ATLOCK v4 instead uses ✅ PBKDF2-HMAC-SHA256 200,000 iterations for password derivation. Then derives a Fernet key. Finally encrypts vault entries using authenticated encryption. Password │ PBKDF2-HMAC-SHA256 200,000 rounds │ Derived Key │ Fernet AES Encryption │ Encrypted Vault This means tampering with encrypted vault data is detected automatically. 🛡️ 2. File Guard Uses Windows ACLs Instead of hiding files... Instead of renaming files... ATLOCK actually interacts with Windows security. It modifies NTFS Access Control Lists. User │ Open File │ Windows ACL │ Access Denied If native APIs aren't available, it gracefully falls back to an alternate protection method. That fallback makes the software more portable without sacrificing functionality. 🚨 3. Intruder Detection is Event Driven Authentication failure doesn't simply increase a counter. Instead every event escalates. Wrong Password #1 ↓ Photo Capture ↓ Notification ↓ Wrong Password #3 ↓ 10 Second Video ↓ Alarm ↓ Hard Lock This creates an actual intrusion timeline instead of merely rejecting authentication. 🎥 4. Forensic Evidence Collection ATLOCK automatically captures: 📸 timestamped photographs 🎥 timestamped videos These are stored separately inside dedicated directories for later inspection. Rather than overwriting evidence, each capture receives a unique timestamp and random identifier. 🔔 5. Security Notifications Another small feature I enjoyed building was the notification system. Every security event becomes structured metadata. Event ↓ Timestamp ↓ Category ↓ Masked Credentials ↓ Photo ↓ Video Notice one important detail: Passwords are never stored in plaintext. Only masked representations are logged. Example: A******** (8 chars) instead of Admin123 🔒 6. System Lockdown ATLOCK also attempts to reduce bypass opportunities. During lockdown it uses Windows-specific mechanisms including: keyboard hook task manager monitoring workstation locking fullscreen interface This is less about being impossible to bypass and more about significantly increasing the effort required. ⚙️ 7. Defensive Design Some implementation choices I intentionally made: ✔ background worker threads ✔ graceful degradation ✔ feature isolation ✔ exception logging ✔ modular components Instead of crashing when optional dependencies are unavailable, the application simply disables that capability. That makes deployments significantly more resilient. 📂 Project Organization ATLOCK ├── Lockdown Engine ├── File Guard ├── Password Vault ├── Intruder Detection ├── Notification Manager ├── Camera Engine ├── Settings Manager ├── Sound Engine └── UI Each module owns exactly one responsibility. 📈 Why I Built It I wasn't trying to build another password locker. I wanted to explore what happens when you combine Windows internals modern cryptography desktop UI event-driven security forensic logging inside one Python application. The result became ATLOCK v4. 🚀 Future Ideas Secure cloud synchronization Hardware security key support Multi-device vault Signed update system Plugin architecture Memory hard KDFs (Argon2) Cross-platform security backend Final Thoughts ATLOCK v4 isn't trying to compete with enterprise endpoint security platforms. Instead, it's an exploration of how far a desktop application can push layered security by combining cryptography, operating system features, and intrusion response into a single cohesive architecture. 🔗GitHub 👉https://github.com/Akhouri-Anmol-Kumar/ATLOCK 🔗Direct Download(ATLOCK)👉 https://github.com/Akhouri-Anmol-Kumar/ATLOCK/releases/download/v4.0/ATLOCK.zip If you're interested in desktop security engineering or Windows internals, I'd love to hear your feedback. "if it's Akhouri Systems Software then for sure your windows is running THE BEAST" ---- Its Akhouri systems guarantee. "We Build What Other Forgot To Fix"