🔒 How I Built ATLOCK v4 — A Deep Technical Breakdown of a Windows Security Suite

"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"