Hello Akala,
it's probably not handled by the code.
I will have a look.
Regards
Fabrice
Le 2017-08-25 à 09:40, Akala Kehinde a écrit :
Hello Fabrice,
JUst tested this out. Had multiple scanners (WMI and Nessus) attached
to same connection profile. Found out only one scanner can be active
Hello Fabrice,
JUst tested this out. Had multiple scanners (WMI and Nessus) attached to
same connection profile. Found out only one scanner can be active at a time
i.e. that on top. The ones below dont trigger.
Is PF coded this way?
Regards,
Kehinde
On Wed, Aug 23, 2017 at 2:34 PM, Fabrice
If Nessus support it then why not but it need to be coded in teh Nessus6
module.
Regards
Fabrice
Le 2017-08-23 à 03:01, Akala Kehinde a écrit :
> Hello Fabrice,
>
> Basically what I was trying to ask is if it's possible to attache more
> than 1 scan policy to a Nessus scan engine. Don't think
Hello Fabrice,
Basically what I was trying to ask is if it's possible to attache more than
1 scan policy to a Nessus scan engine. Don't think it's possible. Except
you create another engine with another policy, and attach both scan engines
in the connection profile.
scan.conf
[ENGINE1]
Hello Akala,
yes, based on the os.
Regards
Fabrice
Le 2017-08-18 à 15:44, Akala Kehinde via PacketFence-users a écrit :
Hello guys.
Will like to know if it's possible to have more than 1 nessus scan
policy configured on PF.
Regards,
Kehinde
Hello guys.
Will like to know if it's possible to have more than 1 nessus scan policy
configured on PF.
Regards,
Kehinde
--
Check out the vibrant tech community on one of the world's most
engaging tech sites,
