Community Blogs

AIX Requirements Imperva requires the DB to be started if it’s running on AIX, why is this an Imperva requirement? This is not an Imperva requirement, it is dictated by AIX design and processing This situation involves system call updates and how they are made available to the processes that need those calls to function as expected Specifically the system calls updated or newly added by the agent These system-calls are updated directly to the primary system-call table – aka svc table In addition to the main svc table there are copies of this table which are used by the various processes/applications In order to have the updated ...

VM Admin is resisting requests to reserve resources for the Imperva instance. What is the proper response? VM advantages Imperva recognizes that there are many advantages of deploying virtual instances One primary advantage is that it allows the instances/hosts on a VM to share available resources The idea is that if an instance needs more CPU or memory it can request it when needed In this situation resources are not reserved and only allocated when needed/requested. This solution works for applications or databases where operations can be queued or retried In the case of a security appliance this is not an ...

When performing DAM – Database Activity Monitoring – the legacy deployment is to install the agent on the DB server, register the agent and assign it to a specific gateway. There is also an option to assign a secondary gateway for fail-over purposes.   This model worked well for years, but as audit requirements changed so did the need to monitor database activity. There are customer deployments that have over 100 agents deployed and actively monitoring. The legacy deployment was simply not sufficient to support large agent deployments. There needed to be more flexibility and visibility.   DAM Clusters were introduced just for that reason. ...

#CloudWAF(formerlyIncapsula)

Where do I find EOS and EOL information and what is the difference between the two. EOL/EOS information can be found at https://www.imperva.com/services/technicalsupport Search for Software schedule and it will take you to the tabs EOL – end of life – Software When a software version reaches EOL no more patches will be released for that version In addition there will be no bug fixes released Support will still troubleshoot issues during the EOL period but it will require being on the latest patch for that version If the issue is not a known issue with a corresponding workaround or is not resolved by the latest available patch, an upgrade ...

General questions customers have about Licensing, MX SoM and more License are applied to the MX and SoM There is no license on the GW There are two types of licenses - perpetual and Flex-Protect A perpetual license is for a fixed amount of devices and services and typically cover 1 calendar year, and are deployment specific A Flex-Protect license can cover a variety of devices depending on the requirements, and cover multiple deployments – on-prem, AWS/AZURE, or hybrid What are Activation's and how are they used? Activation's are for virtual deployments An activation is the ability to create a new license on demand Under Flex-Protect ...