Imperva Cyber Community

Expand all | Collapse all

Data Security Coverage Tool

  • 1.  Data Security Coverage Tool

    Posted 19 days ago
    I am wondering if there is an option to extract or export the full compatibility matrix information.
    For a handful of OS/DB/Agents combinations, the tool may be useful. Anything more than that, its quite painful as they JS is slow and multiple correlations have to be made to get the correct combination.

    For example, selecting a version of the agent shows a list of OSs and DBs that are supported. However, it does not imply that every OS shown in the list will support every DB version in the list.

    An option for data to be sync or exported will be useful.

    spencer chong
    Standard Chartered Bank

  • 2.  RE: Data Security Coverage Tool

    Community Manager
    Posted 18 days ago
    @spencer chong

    Thank you for the post. We are working on a reporting option, but as of now there is no simple way to implement that today in the tool

    Christopher Detzel
    Community Manager

  • 3.  RE: Data Security Coverage Tool

    Posted 15 days ago
    Hi Christopher,
    Thanks for the quick response. Looking forward to the availability of the reporting tool.
    A suggestion: It would be good if lists based on DB type or OS Type is made available as files for each agent version. 


    spencer chong
    Standard Chartered Bank

  • 4.  RE: Data Security Coverage Tool

    Posted 14 days ago
    You have 2 options to get the information.
    1. Select any one of the Agent version or GW/MX version or OS version or DB version using the below link.
    2. Download the whichragent file from FTP and Run the below command in the command prompt for Non-windows systems.
    ./whichragent -v 14.0


    Mayuranathan Palanichamy

  • 5.  RE: Data Security Coverage Tool

    Posted 8 days ago
    ​Hi Mayuranathan,
    Thanks for the suggestions. However, (1) becomes very tedious when we have many versions of OS and multiple OS versions.
    And there are no options to export the information for offline analysis. The final output is also a play with the JS formatting and hence it makes copying or scrapping of the info very tedious.

    I actually did a look at the whichscript file in hope to reverse engineer that. But even for Unixes, it relates more to the kernel version. I don't find info relating to the DB in the script. I might have missed it though.