Skip to content
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

As tech lead, I need a new permissions group for ACF OCIO #1358

Closed
4 of 12 tasks
ADPennington opened this issue Oct 1, 2021 · 15 comments · Fixed by #1668
Closed
4 of 12 tasks

As tech lead, I need a new permissions group for ACF OCIO #1358

ADPennington opened this issue Oct 1, 2021 · 15 comments · Fixed by #1668
Assignees
Labels
backend compliance OCIO-related compliance tasks security

Comments

@ADPennington
Copy link
Collaborator

ADPennington commented Oct 1, 2021

Description:
As we are now storing our ZAP scans, we need to give OCIO read access to them. The simplest way to do so is to create a new group with access only to our ZAP and ClamAV logs and objects.

Acceptance Criteria:

  • New ACF OCIO group is created in our database by default
  • New group does not have STTs nor Regions associated to it
  • ACF OCIO group should have read-only access to DAC security scans (e.g. OWASP scans, ClamAV scans)
  • ACF OCIO group should not have access to view other areas of DAC nor the Frontend where feasible
  • Testing Checklist has been run and all tests pass
  • README is updated, if necessary

Tasks:

  • Migration for creation of this new group by default
  • Exhaustive listing of relevant permissions for accessing backend security forms and objects
  • Relevant user instantiation excludes STTs and Regions
  • Document group permissions matrix in this Readme
  • User-facing documentation for how ACF OCIO staff can login to DAC/Security and access objects (scan pdfs, ClamAV log entries)
  • Run Testing Checklist and confirm all tests pass

Notes:

Supporting Documentation:

Open Questions:

  • Can these users be easily redirected straight to the backend after authentication?
@valcollignon
Copy link

  • apply dev template
  • link README
  • create tasks

Bring up during dev sync.
CC: @ADPennington @abottoms-coder

@ADPennington
Copy link
Collaborator Author

  • apply dev template
  • link README
  • create tasks

Bring up during dev sync. CC: @ADPennington @abottoms-coder

per dev sync, we decided that dev team will take this ticket and scope out tasks given the abovementioned ACs. @valcollignon

@valcollignon
Copy link

@ADPennington are you taking the ticket for this current sprint? Or scoping out tasks for a future sprint?

@ADPennington
Copy link
Collaborator Author

@ADPennington are you taking the ticket for this current sprint? Or scoping out tasks for a future sprint?

@valcollignon -- dev is taking this ticket to scope the tasks. if the tasks are scoped in time for next week's backlog, we can discuss where it would go in our workflow. cc: @abottoms-coder

@andrew-jameson
Copy link
Collaborator

@ADPennington Do we agree this ticket is blocked by #1170 ?

@ADPennington
Copy link
Collaborator Author

@ADPennington Do we agree this ticket is blocked by #1170 ?

@abottoms-coder agree. let's discuss the AC re: this group's access to frontend where feasible. they need it for logging into TDP. and they'd also need a way to get to the backend scans from there. I'd like to better understand what that flow will look like 😃

@valcollignon
Copy link

This issue has been refined from the dev standpoint.

@jorgegonzalez
Copy link

ACF OCIO users should be enforced to utilize PIV card via new AMS integration

Question about this AC, will ACF OCIO all have @acf.hhs.gov email addresses? In which case this AC may already be satisfied @ADPennington @abottoms-coder

@andrew-jameson
Copy link
Collaborator

ACF OCIO users should be enforced to utilize PIV card via new AMS integration

Question about this AC, will ACF OCIO all have @acf.hhs.gov email addresses? In which case this AC may already be satisfied @ADPennington @abottoms-coder

I would expect this assumption is valid and this AC is satisfied.

@jorgegonzalez
Copy link

Can that AC be removed from this ticket then, if we agree it is satisfied?

@andrew-jameson
Copy link
Collaborator

Can that AC be removed from this ticket then, if we agree it is satisfied?

@ADPennington Are you ok with this?

@ADPennington
Copy link
Collaborator Author

removed @jorgegonzalez @abottoms-coder

@jorgegonzalez
Copy link

Just saw this

Can these users be easily redirected straight to the backend after authentication?

If so, do we intend for users in this group to never see the frontend? Redirecting them straight to Django Admin reduces the added complexity of validating this on the frontend. So if that is the desired behavior, I'm updating the PR to support this shortly @ADPennington @abottoms-coder

@ADPennington
Copy link
Collaborator Author

@jorgegonzalez -- @lfrohlich and I just discussed and can confirm that this permission group can be redirected back to security url in DAC. they dont need to do anything on the frontend. maybe access to the profile page, but only if its easy. cc: @abottoms-coder

@reitermb
Copy link

Demoed by @jorgegonzalez on 3/15/2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend compliance OCIO-related compliance tasks security
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants