@manny_singh Still not sure I completely follow; however, on the fact_asset_policy_rule table there is a compliance column that indicates whether the asset is compliant for the particular rule.
This will return either true or false and the table is already being used in the query above as fapr.compliance. I did notice in the example query I provided you it is actually filtering by fapr.compliance = false so only rules that assets aren’t compliant for are being returned at the moment.
If instead you are looking for more details about the rule (description, rationale, remediation) then the dim_policy_rule table will have more of those details.
@manny_singh Unfortunately I’m not aware of a way to get the values of the checks through SQL query reports. I’ll see if anyone else has any suggestions for you or maybe someone else in the community might be able to chime in.
@manny_singh - You will need to setup a Database Warehouse (external) to reference those values you are looking for. Instructions can be found here: Configure Data Warehouse
After that, you will need to construct the SQL query using the schema found here: Data Warehouse Schema
@Aniket-Menon
I looked at the database schema already , to me it looks like the table that needs to be referenced is dim_policy_rule_test , But i am totally confused how to construct this query.
I looked at the option of connecting to database using sql query editor tools. Can i not connect directly to the database ?
@manny_singh - you can connect directly once you setup the Data Warehouse. It will have to be an external Postgres database. This will be a separate database from the one that comes with the Nexpose / InsightVM console.
Manny, something that is important to remember is that for the reports within the ui you are essentially just working within a view. You can force access to the db directly through modifying authentication configurations but it’s likely not what you’re hoping for. If you are looking for full db query access the warehouse option that was mentioned by Aniket is one of your safest options and provides the _test tables you are trying to use. Otherwise using the reporting view you’ll be restricted to what is presented in the view’s datamodel which is different from what is available in the warehouse option. https://nexpose.help.rapid7.com/docs/understanding-the-reporting-data-model-dimensions for dimensions and https://nexpose.help.rapid7.com/docs/understanding-the-reporting-data-model-facts for facts.
The view can technically be modified on the console but it’s not something that I would recommend in most cases. It doesn’t look like the idea portal exists anymore but I would still suggest filing a feature request to have the information made available in the view for reports. https://kb.help.rapid7.com/docs/suggesting-a-feature-or-enhancement
I updated the query again to remove the spaces that was result of removing xhtml tagged data and also fixed the proof field which was not parsing out all text with the use of htmlToText.
SELECT
dp.policy_id, dp.title as policy_title, dpr.rule_id, dpr.title as policy_rule_title,
dp.benchmark_name, da.ip_address, da.host_name, dpr.description, dp.category,
fapr.date_tested, (regexp_replace(fapr.proof,'<[^>]*>|^\s+|\s\s+','','g')) as proof, fapr.compliance,
dpr.severity, (regexp_replace(dpr.rationale,'<[^>]*>|^\s+|\s\s+','','g')) AS rationale, (regexp_replace(dpr.remediation,'<[^>]*>|^\s+|\s\s+','','g')) AS remediation
FROM fact_asset_policy_rule fapr
JOIN dim_policy dp on dp.policy_id = fapr.policy_id
JOIN dim_policy_rule dpr on dpr.policy_id = fapr.policy_id and fapr.rule_id = dpr.rule_id
JOIN dim_asset da on da.asset_id = fapr.asset_id
Team , I have been trying to get the result from policy scan dated back in 2021-10-28 using the the query and tried using WHERE clause and it is still showing results from most recent date ( 2021-11-16.
Clause used – WHERE fapr.date_tested< ‘2021-10-30’
What do i need to change in the Query to get the result from 2021-10-28 ?
Manny
Could you post the full query? I double checked the tables/fields against the WHERE clause you posted, but it looks alright at a glance. Seeing the full query might provide some more insight.
@holly_wilsey Thank you for your response , below is the query : I have tested number of time and it is still showing most recent result , however within the console , I can see result of the policy scan that occured on 2021-10-28 but Query always output most recent scan results.
SELECT
dp.policy_id, dp.title as policy_title, dpr.rule_id, dpr.title as policy_rule_title,
dp.benchmark_name, da.ip_address, da.host_name, dpr.description, dp.category,
fapr.date_tested, (regexp_replace(fapr.proof,'<[^>]*>|^\s+|\s\s+','','g')) as proof, fapr.compliance,
dpr.severity, (regexp_replace(dpr.rationale,'<[^>]*>|^\s+|\s\s+','','g')) AS rationale, (regexp_replace(dpr.remediation,'<[^>]*>|^\s+|\s\s+','','g')) AS remediation
FROM fact_asset_policy_rule fapr
JOIN dim_policy dp on dp.policy_id = fapr.policy_id
JOIN dim_policy_rule dpr on dpr.policy_id = fapr.policy_id and fapr.rule_id = dpr.rule_id
JOIN dim_asset da on da.asset_id = fapr.asset_id
WHERE fapr.date_tested< '2021-10-30'
My initial thought is that you would need to include the full date + time in your comparison value for the timestamp, or else there may be results outside of your intended date range. It depends on how the timestamps in the fapr.date_tested field are actually formatted, though. You could try something like:
WHERE fapr.date_tested < '2021-10-30 12:00:00.000000'
If you see no results, it sounds like it could be a date formatting issue. I would copy an example date from the date_tested column and just update the date to the desired year/month/day to ensure it retains the proper formatting. If that doesn’t work, I suspect it may be due to the table itself.
I do see result if the Date is WHERE fapr.date_tested > ‘2021-10-30 12:00:00.000000’ however there is 0 result for WHERE fapr.date_tested < ‘2021-10-30 12:00:00.000000’ , I tried copying example date from the date_tested column as you suggested however it still doesn’t work.
Do we have any other suggestion? to fix or workaround ? I also tried to use fact_asset_scan_policy table with another query both fact_asset_scan_policy and fact_asset_policy_rule are behaving exactly same.
Currently using the SQL query below to import the scan results into our ServiceNow custom table. This query also works with the sql export report in InsightVM, but you might need the rename “check_result” tot “compliance”. The WHERE gives me the scan results of yesterday.
SELECT dp.policy_id,
dp.title as policy_title,
dpr.rule_id,
dpr.title as policy_rule_title,
da.ip_address,
da.host_name,
fapr.asset_id,
dpr.description,
fapr.date_tested,
htmlToText(fc.proof) as proof,
fc.check_result,
dpr.severity,
(regexp_replace(dpr.rationale,’<[^>]>|^\s+|\s\s+’,’’,‘g’)) AS rationale,
(regexp_replace(dpr.remediation,’<[^>]>|^\s+|\s\s+’,’’,‘g’)) AS remediation
FROM fact_asset_policy_rule fapr
JOIN dim_policy dp on dp.policy_id = fapr.policy_id
JOIN dim_policy_rule dpr on dpr.policy_id = fapr.policy_id and fapr.rule_id = dpr.rule_id
JOIN dim_asset da on da.asset_id = fapr.asset_id
JOIN fact_asset_policy_rule_check fc on fc.policy_id = fapr.policy_id and fc.rule_id = fapr.rule_id AND fapr.asset_id = fc.asset_id
WHERE date(fapr.date_tested) = CURRENT_DATE - 1
edit: you can change CURRENT_DATE - 1 to YYYY-MM-DD (between quotes) to get the scans for that date.
