GSA / GSA/GEAR3

ATOType or new additional field for LiSaaS and MiSaaS systems?

Open
#590 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
12
Forks
8
Avg merge
23h 38m
Merged PRs (30d)
15

Description

First time caller, long time listener to GEAR and using it day to day on the inside of GSA. 👋 There is a collection of security officers, project managers, developers, UXers, and all nature of security enthusiasts [in a Slack channel](https://gsa-tts.slack.com/archives/CG8SNAEQM/p1738353169167839). Someone asked if there is a way to filter on LiSaaS or MiSaaS systems in the prod deployment of GEAR on the GSA network. I found evidence of some records that _could_ be Low or Moderate but this custom ... let's say authorization type ... by looking at system records, but nothing in the FISMA view is returned. Is it possible to filter the data from the ATOType with the API and render those specific authorization types with this data or in a new column?

https://github.com/GSA/GEAR3/blob/83f7f3f518b0e376ea81aee41cbabf63aeb475d1/api/models/fisma.model.ts#L10

https://github.com/GSA/GEAR3/blob/83f7f3f518b0e376ea81aee41cbabf63aeb475d1/src/app/components/modals/systems-modal/systems-modal.component.html#L135-L138

I am not sure if you have received a feature request before, but this feature would be most helpful if added. If I am not understanding the right collection of filter queries and it is already supported, please let us know! I looked at the Excel and SQL dumps and couldn't find such an existing system, so I cannot be sure myself.

If unfamiliar, GSA has documentation on those authorization types in their [IT Standards Profiles policy document](https://insite.gsa.gov/directives-library/gsa-information-technology-it-standards-profile?term=misaas). I hope that helps.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with api/models/fisma.model.ts around the ATOType definition and src/app/components/modals/systems-modal/systems-modal.component.html around the existing system fields. Trace how authorization data reaches the FISMA view and determine whether the requested LiSaaS and MiSaaS values are available. Done means those authorization types can be filtered and displayed consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.