I want to build something actually worth using.

When I started ATLOCK, the goal was simple:

Build a Windows security application.

But somewhere along the way, that goal changed.

Now I want to build something that makes me stop and ask:

“Would I trust this with my own machine?”

And if the answer is not yet...

Then I have more work to do.

🛡️ ATLOCK v4

ATLOCK is my attempt at building a local-first Windows security suite that brings multiple security capabilities into one portable application.

🔒 System Lockdown
🛡️ NTFS/ACL File Protection
🔑 Local Encrypted Password Vault
📸 Intruder Ops
🔔 Security Notifications
⚙️ Portable Deployment

But honestly?

Those features aren't enough.

A security application isn't good because it has a long feature list.

It's good when someone tries to break the assumptions behind those features—and the application survives.

🔥 So I'm Taking a Different Approach

I'm actively trying to attack my own design.

Not literally with some Hollywood hacker nonsense 😂.

I'm talking about questions like:

🔑 What happens to the vault key after unlock?

PBKDF2 can make password guessing expensive.

Fernet can provide authenticated encryption.

But what happens after the key is derived?

Where does it live?

What exists in process memory?

What happens if someone can inspect the running process?

Those questions are uncomfortable.

Good.

Security engineering should be uncomfortable.

📸 What About Intruder Ops?

Webcam-based intrusion detection sounds cool on a feature list.

But then the uncomfortable questions start:

What if detection is wrong?

Who can access the captured evidence?

What happens if someone copies the evidence directory?

Are the files protected by the same security model as the vault?

What happens on a machine with multiple local users?

Suddenly the feature isn't:

“Take a photo when something suspicious happens.”

It's:

“Create, store, protect, and eventually dispose of highly sensitive evidence.”

That's a completely different engineering problem.

🧠 This Is What Building ATLOCK Has Taught Me

Security isn't a checkbox.

You don't get to say:

AES ✅
PBKDF2 ✅
ACLs ✅
Authentication ✅

and declare victory.

Every security mechanism creates another set of questions.

And sometimes the biggest vulnerability isn't the algorithm.

It's everything around the algorithm.

🚨 I'm Not Going To Pretend ATLOCK Is Perfect

This is probably the most important thing I've learned.

I could write:

“Military-grade security.”

“Unbreakable encryption.”

“Ultimate Windows protection.”

and it would probably sound great in marketing.

But that's not engineering.

I'd rather say:

Here's what ATLOCK currently does.

Here's what I think is secure.

Here's what I'm uncertain about.

Here's what I'm testing next.

And then let other developers tear it apart.

🔥 Because That's How I Want To Build

Not:

Build → Ship → Forget

But:

Build → Test → Question → Break → Fix → Repeat

That's the loop.

And I'm nowhere near finished.

🚀 ATLOCK v4 is available

If you're a Windows user, developer, or security enthusiast:

Try it.

Don't just compliment it.

Challenge it.

Find something I missed.

👉 ATLOCK v4: [https://github.com/Akhouri-Anmol-Kumar/ATLOCK]

And if you're a security developer:

What would YOU attack first?

Because I'm genuinely interested in finding out.

ATLOCK

"We Build What Others Forgot To Fix"