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

Epic: Obtain an ATO for FAC #725

Closed
32 of 33 tasks
JeanMarie-PM opened this issue Jan 9, 2023 · 7 comments · Fixed by #1141
Closed
32 of 33 tasks

Epic: Obtain an ATO for FAC #725

JeanMarie-PM opened this issue Jan 9, 2023 · 7 comments · Fixed by #1141
Assignees
Labels
compliance Stuff which may relate to a specific requirement or timelines for resolution

Comments

@JeanMarie-PM
Copy link
Contributor

JeanMarie-PM commented Jan 9, 2023

Must/required for assessment

  1. 3 of 3
    MUST compliance
    ChrisB-16
  2. MUST compliance
    ChrisB-16
  3. MUST compliance
    ChrisB-16
  4. MUST compliance
    ChrisB-16
  5. MUST compliance
    JeanMarie-PM
  6. 6 of 6
    MUST compliance
    JeanMarie-PM mogul
  7. 1 of 1
    MUST compliance
    asteel-gsa mogul
  8. 4 of 4
    MUST compliance
    mogul
  9. MUST compliance
    ChrisB-16 JeanMarie-PM
  10. SHOULD compliance
    JeanMarie-PM
  11. 9 of 9
    MUST compliance
    ChrisB-16 JeanMarie-PM
    mogul
  12. 2 of 2
    UNKNOWN compliance
    ChrisB-16
  13. 2 of 4
    MUST compliance
    mogul
  14. 1 of 4
    MUST compliance
    ChrisB-16 JeanMarie-PM
    jadudm mogul
  15. MUST compliance
    asteel-gsa mogul
  16. SHOULD compliance security
    ChrisB-16 JeanMarie-PM
    mogul
  17. 1 of 1
    SHOULD compliance
    JeanMarie-PM
  18. 6 of 9
    SHOULD compliance
    asteel-gsa mogul
  19. SHOULD compliance security
    ChrisB-16 JeanMarie-PM
    jadudm mogul
  20. 0 of 2
    REVISIT compliance
    mogul
  21. COULD compliance security
    ChrisB-16 JeanMarie-PM
@JeanMarie-PM JeanMarie-PM self-assigned this Jan 9, 2023
@JeanMarie-PM JeanMarie-PM added this to the M08: Initial release milestone Jan 9, 2023
@JeanMarie-PM
Copy link
Contributor Author

@JeanMarie-PM
Copy link
Contributor Author

Need the following doc to be reviewed. In particular, are there other information types that we need to include in Table 3.2? https://docs.google.com/document/d/1k5VxDeKqGS3svqZGgeNlX6HswWIXJ9Jhf67dhvZmze4/edit?usp=sharing
@mogul , can you take a look please, or let me know who can do this?

@mogul
Copy link
Contributor

mogul commented Jan 31, 2023

That looks accurate AFAIK.

@JeanMarie-PM
Copy link
Contributor Author

Status on 02/15/23:

  • DIA , FIPS-199 and PTA awaiting approval by Ryan Palmer.
  • System architecture diagram has been updated and needs to be discussed with Ryan.

@JeanMarie-PM
Copy link
Contributor Author

JM started working on PIA in archer. Waiting for Chris to get access to archer.

@JeanMarie-PM JeanMarie-PM added compliance Stuff which may relate to a specific requirement or timelines for resolution and removed engineering labels Apr 19, 2023
@JeanMarie-PM JeanMarie-PM linked a pull request May 22, 2023 that will close this issue
@mogul mogul reopened this May 23, 2023
@mogul mogul mentioned this issue May 25, 2023
21 tasks
@jadudm jadudm removed this from the M08: Initial release milestone Jun 17, 2023
@mogul mogul changed the title Obtain an ATO for FAC Epic: Obtain an ATO for FAC Jul 25, 2023
@mogul mogul self-assigned this Jul 25, 2023
@mogul
Copy link
Contributor

mogul commented Jul 29, 2023

@jadudm can you please confirm that we are definitely going to be adding an Oracle DB to work with during ETL? If so I will roll all three of these into a separate issue.

Image

@jadudm
Copy link
Contributor

jadudm commented Sep 20, 2023

LATO obtained. Future work will be tracked through the board and future epics.

@jadudm jadudm closed this as completed Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compliance Stuff which may relate to a specific requirement or timelines for resolution
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants