The offence is not bad either. We move the discussion in an antagonist/protagonist sort of way and the discussion becomes like an Indian series, which the people love to hate and hate to love.Comodo defence is impenetrable... unless you have the capabilities of a zero-day exploit using "D"LL hijacking!
It can mainly be countered by SAC now (because usually malicious dll will be unsigned, unless code signing abuse was applied) but also, in a programmatical way behavioural monitoring (cloud based) can contain information about the Process-DLL relationships (extracted through telemetry) and detect anomalies. But DLL hijacking is just one way to abuse trusted process to load malicious code.
Loading code behind trusted processes is facilitated in a few ways usually:
Most likelyPerhaps all those old regressive Indian dramas on TV programmed me to love outdated tech like Comodo!
SOS… (and maybe a McAfee Premium 5-year/5-device license)!
Yeah, that’s true. It’s not funny anymore when it costs you.HaHas turn to WoWs... The joke's not so funny when it comes with a price tag!
Is that 1 vote yours, or am I mistaken?HaHas turn to WoWs... The joke's not so funny when it comes with a price tag!
Not yours, Rashmi’s vote. I know it’s not yours. I am expecting 2 more votes.
If I had been using CIS/CF, that would have been fine, and even if I had voted, I would have admitted that I voted YES or NO.
What a shame, just because I was ✍ my manifesto, you replied, perhaps to mitigate this vulnerability?
Or maybe you want to tone it down like 0Pathy. Like, you activate ARP blocking, block PowerShell to prevent attackers from delivering Metasploit payloads, another thing would be to monitor that folder ../../../ProgramData/Microsoft/Windows/Start Menu/Programs/Startup/ maybe you have another card up your sleeve? 
