-
Notifications
You must be signed in to change notification settings - Fork 94
Issues: GSA/fedramp-automation
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[Feedback]: add .bash_profile to constraints readme manual install instructions
#761
opened Oct 7, 2024 by
kyhu65867
2 of 12 tasks
POAM Deviation Requests
leadership review
scope: documentation
wait-for-review
#373
opened Dec 13, 2022 by
TelosPO
1 of 16 tasks
[Feedback]: Component[@type = Interconnection] prop requirements support
#576
opened Mar 26, 2024 by
Telos-sa
1 of 12 tasks
Adding FedRAMP Custom Prop for Diagram ID for Inventory Items
enhancement
New feature or request
leadership review
scope: documentation
#148
opened Jul 27, 2021 by
ohsh6o
4 of 6 tasks
Discrepancy between FedRAMP SSP Guide, SSP Baseline, and OSCAL Schema with regard to Control Origination
scope: documentation
#212
opened May 5, 2022 by
telosBA
3 of 16 tasks
Discrepancy between FedRAMP and NIST prop name in back-matter
scope: documentation
scope: templates
#216
opened May 5, 2022 by
telosBA
3 of 16 tasks
Additional control statement guidance/requirement discrepancy
bug
Something isn't working
scope: baselines
#225
opened May 16, 2022 by
GaryGapinski
FedRAMP OSCAL catalog and profile additional requirement and guidance statements have deficiencies
bug
Something isn't working
scope: baselines
#231
opened Jun 8, 2022 by
GaryGapinski
responsible-role
should be unnecessary for inapplicable control requirements
bug
#233
opened Jun 16, 2022 by
GaryGapinski
Automation is difficult with OSCAL catalog named parameters
triage needed
#253
opened Aug 25, 2022 by
degenaro
2 of 16 tasks
POA&M Guide Section 4.2.4 Includes erroneous props
scope: documentation
#258
opened Sep 8, 2022 by
telosBA
2 of 16 tasks
How to address facet name in POA&M section 4.2.4
scope: documentation
#259
opened Sep 8, 2022 by
telosBA
2 of 16 tasks
What are the use cases for risk statement?
scope: documentation
#260
opened Sep 8, 2022 by
telosBA
2 of 16 tasks
What are the allowed values for Backmatter’s Resource “type” prop, specifically for Attachments 9 and 13?
scope: documentation
scope: templates
#345
opened Oct 26, 2022 by
telosBA
3 of 16 tasks
Create Example FedRAMP OSCAL Templates with Examples of Embedded ZIP Archives
enhancement
New feature or request
leadership review
scope: documentation
scope: examples
scope: templates
#123
opened Jul 4, 2021 by
ohsh6o
11 of 13 tasks
The requirement for having every resource be referenced should be removed
leadership review
scope: constraints
scope: documentation
#358
opened Nov 3, 2022 by
telosBA
2 of 16 tasks
[Question]: Do Assessment Objective ODPs need to be included in OSCAL SSP?
#1058
opened Dec 31, 2024 by
Telos-sa
3 of 12 tasks
POAM Observations
leadership review
scope: documentation
wait-for-review
#379
opened Jan 16, 2023 by
TelosPO
16 tasks
Definition for Likelihood, impact and priority
scope: documentation
#380
opened Jan 16, 2023 by
TelosPO
14 tasks
Risk Log Requirements
scope: documentation
wait-for-review
#383
opened Jan 23, 2023 by
TelosPO
14 tasks
Translation support between Assessment Procedure and Objective Label
enhancement
New feature or request
leadership review
triage needed
#398
opened Mar 27, 2023 by
Telos-sa
2 tasks
Duplicate Response Points in both the Assessment Procedures and Baseline Profile
bug
Something isn't working
model: poam
model: sap
model: sar
scope: baselines
scope: templates
#402
opened Mar 28, 2023 by
Telos-sa
Response Point for Objective too low to cover entire control statement (si-4.24)
bug
Something isn't working
model: ssp
scope: baselines
#404
opened Mar 29, 2023 by
Telos-sa
1 task
Confirmation that these Tests OBJECTIVES from SRTM are legacy
scope: baselines
scope: documentation
#409
opened Apr 20, 2023 by
Telos-sa
2 tasks done
The requirement of having one user per responsible-role should be removed
leadership review
scope: constraints
scope: documentation
#356
opened Nov 3, 2022 by
telosBA
3 of 16 tasks
Previous Next
ProTip!
Adding no:label will show everything without a label.