- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
07-22-2025 10:26 AM
07-22-2025 12:58 PM
While it would be nice to have a more "rubust" scheduling method, there are a couple of work arounds that you may help. The first is to change the scheduling frequency in Runtime Security -> System -> Scan -> Agentless. However, due to verying lengths of scans, this may cause scans to run when you don't want them to. Keep in mind, though, that as soon as you change this setting and save it, the scan will kick off, and continue kicking off based on the time you saved.
Another option is to use the Agentless API endpoints to automate scan schedules. You could schedule a script to run, check on whether not a scan is in progress, start a new scan if it is not, and of course, stop a scan if it is running when you don't want it to. Of course, you could use cron, or @now, or any variety of scheduling tools for this.
Hope this helps!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!