Advice Request Regarding on NVT EXE Radar PRO?

Please provide comments and solutions that are helpful to the author of this topic.
Status
Not open for further replies.
@Davidov: What do you mean? Voodoshield provide as much as possible an anti-exploit functionality that blocks any possible scripts to execute same goes to NVT too.
 
@Davidov: What do you mean? Voodoshield provide as much as possible an anti-exploit functionality that blocks any possible scripts to execute same goes to NVT too.
Apparently VoodooShield had integrated a basic anti-exploit function. I don't think EXE Radar Pro has that, at most what it does have is the "Vulnerable process" function which I think could help protect processes from being exploited. Though other users like @Umbra and @hjlbx could confirm or deny that.
 
Apparently VoodooShield had integrated a basic anti-exploit function. I don't think EXE Radar Pro has that, at most what it does have is the "Vulnerable process" function which I think could help protect processes from being exploited. Though other users like @Umbra and @hjlbx could confirm or deny that.

That's what I thought too.
Possibly what could happen is that in NVT you can whitelist them and put it into vulnerable process. Then set it to alert mode. But that's about it.
Correct me if I'm wrong. :oops:

Anyway, side topic here.
Another question on NVT too.

Recently I've been updating softwares like ZAM, EIS and such.
I realise when NVT set to Alert mode, it prompt twice: one is exe and another one is TMP.
Is that normal? Thought NVT wouldn't block/alert those non-exe?
 
NVT doesn't block exploit, but it monitors the child processes, that is maybe why the tmp files are detected.
 
Status
Not open for further replies.

You may also like...