DEV Community

Akhouri Anmol Kumar
Akhouri Anmol Kumar

Posted on

πŸ”’ Why ATLOCK v4 Is Different: Engineering a Security Suite Instead of Just Another Password Locker

"The biggest mistake in desktop security is assuming a password is enough."

That single thought became the foundation of ATLOCK v4.

I didn't want to build another application that asks for a password and calls itself "secure."

I wanted to build something that responds, detects, records, and defends.

🧠 Security Isn't One Feature

Many desktop security apps look like this:

Open App
β”‚
β–Ό
Enter Password
β”‚
β–Ό
Access Granted / Denied

ATLOCK v4 is designed differently.

Authentication
β”‚
β–Ό
Intrusion Detection
β”‚
β–Ό
Evidence Collection
β”‚
β–Ό
Notification
β”‚
β–Ό
System Lockdown

A failed authentication isn't just "wrong password."

It's a security event.

πŸ— Layered Architecture

Instead of putting everything inside one huge file, every subsystem has a dedicated responsibility.

             ATLOCK v4

    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
    β”‚   Lockdown Engine    β”‚
    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
               β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β–Ό              β–Ό              β–Ό
Enter fullscreen mode Exit fullscreen mode

File Guard Password Vault Intruder Engine

β”‚              β”‚              β”‚
Enter fullscreen mode Exit fullscreen mode

NTFS ACL Fernet Crypto Camera System

β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
               β–Ό

      Notification Manager
Enter fullscreen mode Exit fullscreen mode

This modular design makes the project easier to debug, extend, and maintain.

πŸ” Real Cryptography

Security software shouldn't rely on homemade encryption.

ATLOCK v4 uses:

Master Password
β”‚
β–Ό
PBKDF2-HMAC-SHA256
(200,000 iterations)
β”‚
β–Ό
Derived Encryption Key
β”‚
β–Ό
Fernet Encryption
β”‚
β–Ό
Encrypted Vault

The goal wasn't to invent cryptographyβ€”it was to use well-established building blocks correctly.

πŸ›‘ Working With Windows Instead of Around It

Many applications simply:

hide folders
rename files
change attributes

ATLOCK instead leverages Windows security mechanisms where appropriate.

Application
β”‚
β–Ό
Windows Security APIs
β”‚
β–Ό
NTFS Access Control Lists
β”‚
β–Ό
Access Restricted

Using operating system features provides stronger protection than cosmetic hiding techniques.

πŸ“Έ Intrusion Detection

Most applications do this:

Wrong Password

↓

Try Again

ATLOCK treats repeated failures as a sequence of events.

Wrong Password

↓

Photo Capture

↓

Notification

↓

Repeated Attempts

↓

Video Recording

↓

Alarm

↓

Lockdown

The idea is to create visibility into suspicious activity rather than simply rejecting access.

🧡 Responsiveness Matters

Security software often performs multiple operations simultaneously:

encryption
camera capture
notifications
monitoring
UI rendering

Running everything on the main thread would make the application feel sluggish.

Instead, background workers handle long-running tasks while the interface remains responsive.

πŸ”” Logging Without Exposing Secrets

Logs are useful.

Sensitive data isn't.

ATLOCK stores metadata like:

βœ“ Timestamp

βœ“ Event Type

βœ“ Device Information

βœ“ Evidence

βœ“ Result

But avoids recording plaintext passwords.

Even diagnostic information should follow the principle of least exposure.

🧩 Designed for Failure

One engineering lesson I learned:

Every dependency eventually fails.

Instead of crashing when an optional component isn't available, ATLOCK attempts to degrade gracefully.

Camera Available?
β”‚
β”Œβ”€β”€β”€β”€β”΄β”€β”€β”€β”€β”
β”‚ β”‚
Yes No
β”‚ β”‚
Capture Continue

Security shouldn't disappear because one module couldn't initialize.

πŸ’‘ What Makes ATLOCK v4 Special?

Not because it has the most features.

Not because it claims to be "unbreakable."

But because every feature contributes to one design philosophy:

Security should be layered, observable, and resilientβ€”not just password protected.

πŸš€ What's Next?

Current areas I'm exploring:

Hardware security key support
Argon2 for key derivation
Secure cloud synchronization
Signed update mechanism
Plugin architecture
Improved cross-platform compatibility
Final Thoughts

ATLOCK v4 isn't intended to replace enterprise endpoint security or antivirus platforms.

It's an engineering project focused on combining modern cryptography, Windows security features, event-driven intrusion handling, and modular software architecture into a cohesive desktop application.

Building it has taught me that good security isn't about one clever featureβ€”it's about how multiple layers work together.
πŸ”—GitHub: https://github.com/Akhouri-Anmol-Kumar/ATLOCK
πŸ”—Directly Download ATLOCK & Try it: https://github.com/Akhouri-Anmol-Kumar/ATLOCK/releases/download/v4.0/ATLOCK.zip

"We Build What Others Forgot To Fix"

Top comments (0)