SaaS Inline tagged/ marker sites discrepancies

SaaS Inline tagged/ marker sites discrepancies

1169
Created On 04/14/23 21:58 PM - Last Modified 05/27/25 18:31 PM


Symptom


  • The marked/tagged sites are seen unsanctioned that were tagged as unsanctioned last year. 
  • The cloud applications count is increased.


Environment


  • SaaS Visibility
  • SaaS Inline
  • SaaS Security API
  • DLP
     


Resolution


  1. The applications that are tagged “sanctioned / unsanctioned / unknown” are limited to 90 days. The applications will be reclassified to the default state after 90 days.
  2. Cloud applications count increase depends on the traffic on the Firewall. Due to this the number of applications keep on changing and this is normal.
  3. Every time a new application is discovered, the default sanctioned status for that application is sanctioned. For example if there is "Seedprod" application status is "unknown" and it reports as "Unknown initially.
  4. User has the option to change the status to sanctioned/unsanctioned/Unknown.
  5. Due to this, one cannot determine the sanctioned status of the application for every user. An application can sanctioned for one user and might be unsanctioned for another user internally. So, it is up to the user to choose the application status based on their company guidelines.


Additional Information


  • Attached the screenshot and it shows that the total apps for unsanctioned is 28 and might increase later day.image.png


Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000kHgHCAU&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Choose Language