What is your primary use case for Airlock Digital Application Control?

As a Cyber Security Analyst, my primary use case for Airlock Digital Application Control is controlling application executions across the endpoints and servers. I use it to enforce allow-listing policies and prevent unauthorized or potentially malicious executables from running. It helps with application governance by allowing us to improve legitimate software through controlled exceptions while maintaining a consistent security policy. One practical example is when a user needs to run a new application that is not currently approved. Airlock blocks the secured executable based on our application control policy, and I can review the event to verify whether the software is legitimate. If it is approved, I can add a controlled exception rather than changing the overall policy. This makes the process more secure and easier to manage. Airlock works effectively as a preventive layer within our broader security strategy. We use it alongside endpoint security and EDR controls rather than as a replacement for them. The main value is controlling what is actually allowed to execute, which helps reduce the attack surface and gives us stronger application governance across the environment.

Airlock Digital Application Control is used primarily for whitelisting and endpoint security, controlling which applications are allowed to execute on endpoints, preventing unauthorized and potential malicious software from running and reducing overall attack surface. A specific example of whitelisting and endpoint security involves an unauthorized executable being introduced onto an endpoint and attempting to run. Because the application was not on the approval whitelist, Airlock blocked its execution before it could run. Utilizing Airlock has helped prevent malware within our systems, particularly when an unknown executable or application is introduced at an endpoint. Because it is not approved by the application control policy, Airlock blocks it from executing, allowing the security team to investigate it before it can cause an impact.

My main use case for Airlock Digital Application Control is to assist customers in deploying application control to their businesses. I help customers deploy application control by asking them a bunch of scoping questions to determine exactly what they need and how to configure it. Once we understand their requirements, we get access to their environment to deploy the software and assist the customer by training them, running various calls, and looking at the applications running in their environment to show them how to permit or deny those applications. There were a few projects we did that were quite large and were more advisory, where nothing was necessarily deployed, at least in the first phase, but we were assisting in determining if Airlock Digital Application Control was the right product and how they could use it.

My main use case for Airlock Digital Application Control is to implement application whitelisting, prevent unauthorized software from running, and strengthen endpoint security against malware and ransomware. A specific example of how I have used Airlock Digital Application Control in my environment is when this product blocked an unauthorized executable downloaded through email from running on an employee's workstation, preventing a potential malware infection while allowing approved business applications to continue operating normally.

My main use case for Airlock Digital Application Control is to enforce application allow listing across our Windows endpoints so that only approved and trusted software can run. The goal was to reduce the risk of malware, ransomware, and unauthorized applications without disrupting normal business operations. In our day-to-day work, we use it to review requests for new software, verifying that the application is legitimate and then approve it through the appropriate policy so users can run it without needing local administrator privileges. A typical example is when a business team needs a new finance or engineering application that is not already approved. Instead of giving the user elevated access or creating broad security exceptions, we validate the software, test it on a small group of machines, understand the allow list, and then deploy the policy to the required endpoint. This process has helped us maintain tighter control over our environment while still allowing business teams to get the applications they need in a structured and auditable way. Although there is some ongoing administrative effort, especially when new software versions are released or vendors frequently update their applications, the visibility and control it provides have made endpoint management much more predictable and secure.

Application whitelisting has become increasingly important, and ensuring that we’re not running code unknown to our organization is crucial. The organizations I work for have been using it to effectively whitelist applications known to be in use, and then highlight any applications that aren’t within the remit of the service delivery organizations or the infrastructure organizations, ensuring that we’re only executing known code. One of the use cases for Airlock Digital Application Control that we identified were timer applications; we found applications being used potentially to exfiltrate information. We found people using WhatsApp as well as Signal, which weren’t under the control of the data loss prevention capability within the organization I was working with, so we were able to identify applications that might be missed by DLP. We have certain use cases where users require using scripting languages and programming languages such as Python to run simulations and modeling; this is not something we want every user to be able to do, but it’s allowed us to select which users are allowed to run certain applications and under what scripting languages and programming languages and under what circumstances they’re allowed to run them. This means that it’s not a blanket on or off; it’s about under what context the application can actually run, allowing users to use Python or PowerShell under constrained use cases as opposed to unrestricted access.

My use case for Airlock Digital Application Control is application control.

I primarily use Airlock Digital Application Control for application control.

I use Airlock Digital Application Control for application control, primarily handling servers. The solution manages approximately 1,000 servers with centralized control.

I use Airlock Digital Application Control as part of my role in the security team managing endpoint controls and broader defensive measures. I have been working with the product as part of strengthening our application control strategy, mainly around policy design, fine-tuning, and making sure it fits business requirements without causing too much disruption.

The DevOps team uses the REST API for Airlock Digital Application Control, but I am not part of that team, so I am not directly administering or controlling or using the REST APIs tool. The pre-sales team handles the pricing for Airlock Digital Application Control; I am the technical person who looks after the configuration and administration according to the requirements of the client.