Troubleshooting Security Insights in Security Center Extension

After running a Security Insights job and refreshing the browser, the button doesn't show a running job

This is typically due to failed Run Dates on past jobs from an earlier version. To get these corrected, execute anonymous Apex code:

List<revcult__Security_Insights_Refresh__c> refreshes = new List<revcult__Security_Insights_Refresh__c>(); for(revcult__Security_Insights_Refresh__c refresh : [select id, revcult__Run_Date__c, CreatedDate, name, revcult__Status__c from revcult__Security_Insights_Refresh__c order by CreatedDate]) if(refresh.revcult__Run_Date__c == null) { refresh.revcult__Run_Date__c = refresh.CreatedDate; refreshes.add(refresh); } update refreshes;
      

For more information on executing anonymous Apex code, review the Salesforce documentation.

Remove All Files in a Dev Org from Security Insights Jobs

The files can be removed by executing anonymous Apex code. Use the following:

delete [SELECT Id FROM ContentDocument WHERE Title LIKE '%rawResults%' OR Title IN('linkMap.txt', 'monitoring.txt', 'monitoringScore.txt', 'authentication.txt', 'authenticationScore.txt', 'authorization.txt', 'authorizationScore.txt', 'dataLossPrevention.txt', 'dataLossPreventionScore.txt', 'dataProtection.txt', 'dataProtectionScore.txt', 'dismissedComponents.txt', 'integration.txt', 'integrationScore.txt')];
      

For more information on executing anonymous Apex code, review the Salesforce documentation.

Email Isn't Sent After A Security Insights Job

• Check the Spam folder.
• For a progress report email, two SI jobs must be run before an email is sent.
• There may be an error preventing the email from being sent. An error can occur even if the job finishes and results are shown in the UI. The most common error is the Salesforce daily email limit.

Security Insights Jobs Become “Stuck” for Org That Has WithSecure Installed

WithSecure configurations used to cause Security Insights jobs to become stuck on the “Exploring High Risk Object Access” step. The Secure team worked with the developers of WithSecure and resolved this issue with the 23.2 build of Secure. If an Org is running an older version and encountering this issue, update the version of Secure.

Stored Events Still Appear In Untracked Event Types

Secure doesn't count an event as tracked unless there's data within the table. Even if the option is selected, the stored event isn't removed from the insight.