A new chapter in my Windows security project is taking shape.
A lot of software begins with a feature.
ATLOCK began with a problem worth solving: making file protection easier to access.
Now, I’m working on the next stage of that idea.
Introducing a preview of ATLOCK v5 — currently in development at Akhouri Systems.
⚠️ Development update: ATLOCK v5 has not been publicly released. The features discussed here are part of ongoing development and may change before release.
🧩 The idea: Make security tools easier to reach
Security-related tools can feel disconnected. Users may need to move between different interfaces and workflows to manage different tasks.
With ATLOCK v5, I’m exploring a more integrated experience for Windows.
The goal isn’t to claim that one application can replace every security product. It’s to make selected protection and utility workflows more accessible from one place.
Here’s a glimpse of what’s being built.
🛡️ 1. A broader Security Guard experience
ATLOCK v5 is being developed with a Security Guard area that brings several security-related utilities together.
The current implementation includes work on:
- A Windows Defender dashboard integration
- VirusTotal hash lookup
- A startup-persistence watchdog
- A ransomware canary concept that monitors designated decoy files
These features have different purposes and limitations. They are not a replacement for a dedicated antivirus engine, and their effectiveness depends on implementation, configuration, and the Windows environment.
Still, bringing these tools into a more accessible interface is an interesting engineering challenge.
⚡ 2. Less friction in the file-protection workflow
I’m also working on a Windows Explorer context-menu integration.
The idea is straightforward:
Right-click a file or folder → access ATLOCK actions.
Instead of always opening the main application first, users could access supported actions directly from Explorer.
It’s a small interaction change, but reducing unnecessary steps can make a tool easier to use.
🔐 3. Exploring stronger authentication and key protection
The current development code includes work involving:
- AES-GCM encryption
- Argon2id password-based key derivation
- Windows DPAPI integration
- Optional Windows Hello integration
These components serve different roles in the security design. Their presence alone does not establish that the application is secure; correct implementation, key handling, testing, and threat-model review remain essential.
That’s part of the work: not just adding features, but understanding what each component does and where its limitations are.
🧰 4. More than file protection
The current build also includes work on utilities such as:
- A password vault
- Configurable clipboard clearing
- Notifications and settings
- An emergency network-disconnect option
Some of these capabilities are still being refined. I’m keeping additional details private until there’s more to show.
👀 This is only a partial preview.
🏗️ Building in public — without pretending the work is finished
I want to share the development process while being clear about what is and isn’t ready.
ATLOCK v5 is not available for public download yet. Features may change, and the application still needs appropriate testing and refinement.
The aim is to build thoughtfully, communicate honestly, and avoid making exaggerated security promises.
📦 Want to explore ATLOCK today?
ATLOCK v4 remains the publicly available version.
You can explore the project and its releases here:
👉 Visit the ATLOCK GitHub repository
💬 Join the discussion
If you use Windows or build desktop software, I’d like to know:
What makes a security utility genuinely useful to you?
Is it a smoother workflow, better integration with Windows, understandable controls, or something else?
Share your thoughts below. They can help inform what I focus on as development continues.
Top comments (0)