This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About pripatel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About pripatel
12-23-2022
1Post
0Likes
0Solutions
Dec 23, 2022Last Visited
User
Activity
User
Profile
Latest posts by pripatel
| Subject | Views | Posted |
|---|---|---|
| 993 | 07-13-2022 11:59 AM |
User Badges
Community Statistics
| Member Since | 01-03-2022 12:00 PM |
| Date Last Visited | 12-23-2022 10:51 AM |
| Posts | 1 |
07-13-2022
11:59 AM
Foreign Entity means that a resource is not in an onboarded Prisma Cloud Account, essentially a resource that does not actually map to an ingested resource. It is awareness that some resource is not in our view (not ingested) is triggering this violation. I suggest doing the following:
identify where the foreign entity originates
If that cloud account should be onboarded, get it onboarded
If that cloud account is external, what is the relationship with that cloud account? How did that resource get access?
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
12-23-2022
10:51 AM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks