Now I realised that I should not use to rule to exclude an app if it is not digitally signed. The absence of %SIGNER% creates a vulnerability.Under my local user account, I created a folder called (App Data) in which I store the portable apps such as Hard Disk Sentinel.
Now when I tried to run HDS, OSArmor blocked it and adding HDS to exclusions did not fix the block.
The rule that blocked HDS was "Block processes located in suspicious folders"
And the parent process was explorer.exe
To correctly exclude HDS I had to create a manual rule in exclusions [%PROCESSNAME%: HD Sentinel.exe] [%SIGNER% Janis Mathe].
What this rule basically does is add a process to exclusions regardless of its path.
Now step by step I am building my rules and I am experimenting. I am installing my apps and J am monitoring how OSA reacts.
Instead, one should use the %PROCESS% followed by the app storage path to add it to exclusions.
I am using ABDownloadManager which is an open source download manager that is not digitally signed. It was blockes by OSA and I added it to exclusions using the %PROCESS% rule.

