Cyberlock blocks repeatedly Lenovo Vantage processes, commands and scripts.
If you have been using CyberLock for a long time, it might help to reset your whitelist, especially if you have been through a lot of upgrades. You might see a few block the first day or two, but after that, CyberLock will run a lot better. Better yet, you can perform a clean install...
1) Exit out of CyberLock
2) Uninstall CyberLock and click Yes when asked if you want to delete the settings and logs
3) Restart the computer
4) Install the latest version of CyberLock and register the software
Moving forward this will not be that much of an issue because there are mainly small changes with each release. But long time CyberLock users who have been through tons of upgrades should perform a clean install.
Having said that, I am wrapping up a new feature called "Attack Chains" that will probably help with these blocks. I have believed for a very long time that one of the most important concepts in cybersecurity is the attack chain and parent processes, because this is what provides context to help determine if the process execution flow is malicious or not. For example, powershell can be used for good or bad, and it all depends on the attack chain. The hardwired rules in CyberLock have always done a pretty good job of tracking the attack chain and providing context, but the new Attack Chain feature tracks the entire attack chain, from the initial origin process, all the way to the final process, and there is no limit to the number of items in the attack chain.
As an example, one of the issues this new feature solves is when a script or binary is dropped into AppData from a legit whitelisted app, and the attack chain was lost, so CyberLock was not aware that it was the legit whitelisted app that actually spawned this new script or binary a couple of chains back. But with this new feature, CyberLock will know the entire attack chain from start to finish, and will be able to properly auto allow or block an item because it has the full context.
Here is an example of what one of the attack chains look like...
c:\windows\system32\svchost.exe >> c:\program files (x86)\microsoft visual studio\installer\resources\app\servicehub\services\microsoft.visualstudio.setup.service\vsixconfigurationupdater.exe >> c:\windows\system32\lsass.exe >> c:\windows\system32\efsui.exe >> 1632 >> 12780 >> 12876 >> 12876 >>
Another example of an issue that will be solved is when randomly named folders or files are used, CyberLock can still track the attack chain and auto allow the file because it is aware that the parent process id is a legit whitelisted app, in this case "c:\users\username\desktop\configuredefender.exe".
c:\windows\explorer.exe >> c:\users\username\desktop\configuredefender.exe >> c:\windows\temp\052009150559020213\2\configuredefender_x64.exe >> 9544 >> 2800 >> 6388 >>
Of course we have to be super careful to not let web or vulnerable apps auto allow something they shouldn't, but that is actually pretty simiple with the way CyberLock is coded.
This new feature is also pretty cool because it logs and describes in detail everything that is executing on your system, and I am sure there are tons of other things we can do with this new feature.
This new feature should be ready in a couple of days. Thank you guys!