-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update ILM Playbook for Detailee Use Case #390
Comments
Add use case from issues #591 above Summary section
@idmken I started working on this and sent @JBPayne007 an email with an outline before doing a PR. |
Added use case from issue #591
The detailee use case is dependent on the detailed agency system accepting a outside Agency PIV card for all required physical or logical access. Two examples
More thorough response, we will attempt to import the existing PIV for granting physical access. If they require systems access (logical access) and we cannot load the detailed agency certs onto the existing PIV, the detailed agency may issue an alternate credential for logical access. However, some agency PIV annotate level of access for restricted areas, if the individual requires regular access to our restricted areas, we will either issue a detailed agency PIV with access area number or issue a temp badge which annotates the individual is cleared for restricted access.” |
Placeholder to update the ILM Playbook for a detailed use case. Under step 4 integrate, we can update to include other use cases on integration.
Detailee use case - An Agency A employee is detailed to Agency B. How can Agency B use their ILM system for this existing Agency A employee, but short-term Agency B employee. Can Agency A share HR data to do birth-right provisioning in Agency B? I think the corpus of this use case is how Agency B can provision Agency A employee without issuing them an Agency A piv card and an Agency A email.
The text was updated successfully, but these errors were encountered: