Hi Alex,
Syslog is your best option.
An
action set must be created and then defined as a
followed action for the policies you want syslogged.
For more information on creating action sets, please see:
https://docs.imperva.com/bundle/v13.5-web-application-firewall-user-guide/page/2400.htmFor more information on configuring followed actions, please see:
https://docs.imperva.com/bundle/v12.5-web-application-firewall-user-guide/page/2406.htm------------------------------
Jaired Anderson
Senior Professional Services Consultant
Imperva
Tulsa OK
------------------------------
Original Message:
Sent: 12-31-2019 03:40
From: alex kushnarev
Subject: Imperva AWS deployment issues
Thanks for the help,
there is one more issue that i am facing, i am trying to understand how the logging system works and how i can send the logs to a thirds party log analytics platform and for some reason i can not find any useful guide.
any chances you can help with this one?
Alex.
------------------------------
alex kushnarev
Home
rishon le zion
Original Message:
Sent: 12-30-2019 11:13
From: Daniel Schlomiuk
Subject: Imperva AWS deployment issues
Hi Alex,
Adding to Jaired reply.
Once you add the PPK file, you will be able to connect to the CLI via the following user:
ec2-user
And not with the web console credentials.
------------------------------
Daniel Schlomiuk
Original Message:
Sent: 12-30-2019 08:39
From: alex kushnarev
Subject: Imperva AWS deployment issues
Hi team,
i just deployed the SecureSphere in the AWS and trying to connect via ssh to the gateway/management with the same password i use to connect to the web console. but for some reason it always says to me that the password is incorrect.
also i have some issue connecting to the gateway via web console after the deployment,
i did finish setting up the CloudFron stacks and they finished successfully.
any advice on how to deal with those issues?
Alex.
#On-PremisesWAF(formerlySecuresphere)
------------------------------
alex kushnarev
------------------------------