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 an admin, I need to understand how a new STT user will be validated #210

Closed
2 of 3 tasks
shubhi-raft opened this issue Sep 2, 2020 · 2 comments
Closed
2 of 3 tasks

Comments

@shubhi-raft
Copy link
Collaborator

shubhi-raft commented Sep 2, 2020

Description:
A new user that is a representative of an STT cannot be solely verified via a new users' email domain. In the proposed approach, the onus is on the STT admin to validate new users, however, there may be security concerns around how PII is handled, what is acceptable, and who has access to this information. This issue will document our approach to validating new STT users, assumptions, and any OCIO governance or security controls that need to be accounted for.

AC:

  • Document approach (e.g., artifact for get an input for notional validation process) to validate a new STT user including assumptions that shall be tested in Round 3 and/or future rounds of research

Tasks:

  • Schedule meeting(s) with OCIO, O&M, OFA, 18F, etc., to discuss the current process and future approach
  • Document the meeting notes and update the proposed approach and assumptions, if necessary

Note:

  • This issue is dependent of schedule availability of OCIO, OFA, O&M, and 18F and may be pushed into next sprint if schedules don't align or if more than one meeting is needed.
  • Shubhi will work with Lauren to create a draft a list of attendees that can represent OCIO, O&M, and other OCIO divisions.

Open Questions:

  • What do we need to know for MVP?
    -- Documented in updated roadmap presentation.
  • How might we differentiate between verifying a STT user vs a STT admin?
    -- For OFA MVP, STT admin will be a regional specialist
  • How do we ensure assumptions we are making for STT admins are correct?
    -- Discussing with regional specialists
  • What phase of research do we want to talk to STTs about this? Could be part of the conversation guide for Round 3.
    -- Since round 3 does not include any discussions with regional specialists, this will be a separate discussion. As Regional Staff, I want to approve access a new STT user #322

Answers to OQ:

  • What do we need to know for MVP?
  • How might we differentiate between verifying a STT user vs a STT admin?
  • How do we ensure assumptions we are making for STT admins are correct?
  • What phase of research do we want to talk to STTs about this? Could be part of the conversation guide for Round 3.

Deliverable(s):

@shubhi-raft shubhi-raft self-assigned this Sep 6, 2020
@shubhi-raft shubhi-raft changed the title As an admin, I need to understand security issues around validating a new user As an admin, I need to understand how a new STT user will be validated Sep 30, 2020
@shubhi-raft shubhi-raft added this to the Sprint 5 milestone Sep 30, 2020
@lfrohlich
Copy link
Collaborator

lfrohlich commented Oct 7, 2020

Penyin will send access management documentation for the current TDRS and the latest access management policy.
Section 2 of SSP.
Controls related to access as part of first epic.

@lfrohlich
Copy link
Collaborator

This was done as part of Sprint 5 #63

riatzukiza pushed a commit that referenced this issue Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants