Skip to content

v1.1.4

Choose a tag to compare

View all tags
@osmanonurkoc osmanonurkoc released this 17 Aug 18:36
· 2 commits to main since this release
1.1.4
402f052

SecureAppLocker v1.1.4

This update introduces surgical precision to how you handle temporary executions and dynamic rules, making the Zero-Trust environment much smoother for daily administrative tasks and software installations.

New Features

  • Context Menu "Trusted Run" Integration
    We have integrated a new "Run via SecureAppLocker" option directly into the Windows right-click context menu. This feature allows you to launch any executable with a temporary, one-time "Parent Immunity" after verifying your master password. You can choose to execute the file with standard user rights or elevated administrator privileges. This serves as the perfect solution for running one-off installers, updaters, or trusted scripts without having to permanently add them to your whitelist or lower your system's overall security posture. Once the application closes, the temporary clearance vanishes.

  • Wildcard (*) Support for Trusted Exceptions
    The Audit Logs and Trusted Commands system now fully supports wildcard characters. Modern installers frequently extract themselves into temporary folders using dynamically generated version numbers or random strings (e.g., VSCodeUserSetup-x64-1.132.0.tmp). Instead of constantly updating your exception lists with new file names, you can now define a rule using an asterisk, such as VSCodeUserSetup-*.tmp. The engine automatically converts this into a secure regex pattern, granting seamless access to future updates while keeping your blocked ghost processes list completely clean.

Best Practices & Recommendations

  • Handling Bulk Package Managers (Winget, Scoop)
    When using command-line package managers to perform bulk application upgrades, the operating system often breaks the process tree by delegating the actual installation tasks to background OS services or COM objects. Because of this architectural broken chain, parent-child immunity cannot reliably propagate to the extracted setup files.

    If you have System Tools Hardening enabled, these bulk updates will likely be intercepted and blocked. To ensure a smooth experience, we recommend temporarily disabling the Master Protection Switch (or activating the 5-minute Global Unlock mode) from the Manager UI before initiating bulk upgrade operations with Winget, Scoop, or similar tools.

Full Changelog: 1.1.3...1.1.4

Assets 3
Loading