Skip to content
This repository has been archived by the owner on Jun 5, 2023. It is now read-only.

Investigate External Project Access Scanner Compatibility with CAI #3067

Open
kevensen opened this issue Aug 10, 2019 · 0 comments
Open

Investigate External Project Access Scanner Compatibility with CAI #3067

kevensen opened this issue Aug 10, 2019 · 0 comments
Assignees
Labels
priority: p3 Desirable enhancement or minor bug fix triaged: yes

Comments

@kevensen
Copy link
Contributor

The External Project Access Scanner (referred to hereafter as EPAS) doesn't function the same as other scanners. Consider the following. We are in Organization A with Forseti deployed. A user has access to a project in Organization B. No logs and no API data in Org A expose this fact. Therefore, this information never ends up in Forseti's inventory.

In order to over come this, EPAS iterates over each user in Org A and obtains delegated credentials for each user. Using these delegated credentials, EPAS then queries for a list of projects for which the user has access. This list happens to include projects that or not necessarily in Org A.

This takes an extraordinary amount of time for large organizations. For this reason, EPAS is not included in a periodic run. It must be invoked manually. But this isn't the issue at hand.

The issue is that the CAI may not show a user's relation to projects outside of Org A. This needs to be investigated, confirmed, and hopefully resolved.

@kevensen kevensen self-assigned this Aug 10, 2019
@kevensen kevensen added triaged: yes priority: p3 Desirable enhancement or minor bug fix labels Aug 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: p3 Desirable enhancement or minor bug fix triaged: yes
Projects
None yet
Development

No branches or pull requests

1 participant