My customized policy has not flagged or quarantined violations. What should I do?

If your customized policy is not working properly, follow these steps to resolve it:

1. Log in to the SysCloud Application with your credentials.
2. Check if your policy is active:
   
   1. Log in to SysCloud with your account credentials.
   2. Click “Safety, Security & Compliance”→“Policies.”
      
      
   3. Scroll down and check the status of the policy.
      
      
   4. Toggle the “Status” button to “ON.”

       

      3. Check if the conditions for the customized policy have been set properly:

      a. Click on the policy card on the Threat Center page.
      
      
      b. Click on the policy name to view the policy conditions. 
      
      
   4. Check if the policy was created after the violation had occurred.
   1. Log in to SysCloud with your account credentials.
   2. Click on the policy card on the Threat Center page.
   3. Click “HISTORY.”
      
      
   4. Scroll down to check the first update to view the date on which the policy was created.
      
      5. Check if the policy violator belongs to an Org Unit (OU) or a sub-OU that has been excluded from the policy.

Note:

• If you make changes to a policy or its settings, it will be reflected only in the next scan.
• The violations that had occurred in a file before the policy was altered will not be picked up by the scan. The violations will be checked and flagged if you made any changes in the file after the policy was modified.
• If the file is in a non-native Drive format (such as pdf or CSV), it will not be picked up by the threat card.