UNCLASSIFIED - NO CUI

Skip to content
Snippets Groups Projects
Commit ef81d2a5 authored by Joshua Eason's avatar Joshua Eason
Browse files

Master

parent 4ebd7f06
No related branches found
No related tags found
1 merge request!6Development
[Pipelines]
.gitlab-ci.yml @ironbank-notifications/cht
.gitlab-ci.yaml @ironbank-notifications/cht
[Gitlab Configuration Files]
.gitlab/* @ironbank-notifications/cht
## Summary
The following individuals are requesting access to this project (one per line):
(List or tag all individuals here)
The access level should be:
- [ ] Developer access
- [ ] Remove access
## Definition of Done
- [ ] All accounts have been provided the necessary accesses
/label ~"Access" ~"To Do"
\ No newline at end of file
## Summary
Requesting this application be archived due to one of the following reasons:
- [ ] Version is no longer supported by vendor
- [ ] Application is End-Of-Life
- [ ] License violation.
- [ ] Other. See below.
## Detailed Description
(Please provide a detailed description of why this application should be archived)
## Definition of Done
- [ ] Application has been reviewed for archival
- [ ] Project is officially marked as stale
- [ ] Iron Bank frontend no longer lists application as available or approved
/label ~"Container::Archive"
/cc @ironbank-notifications/archive
\ No newline at end of file
## Summary
Requesting application to be hardened. This is only for initial hardening of a container.
## Version Information
Current version: (State the current version of the application as you see it)
Under support: (Is the updated version within the same major version of the application or is this a new major version?)
## Definition of Done
Hardening:
- [ ] Container builds successfully
- [ ] Greylist file has been created (requires a member from container hardening)
- [ ] Branch has been merged into `development`
Justifications:
- [ ] All findings have been justified per the above documentation
- [ ] Justifications have been provided to the container hardening team
Approval Process (container hardening team processes):
- [ ] Peer review from Container Hardening Team
- [ ] Findings Approver has reviewed and approved all justifications
- [ ] Approval request has been sent to Authorizing Official
- [ ] Approval request has been processed by Authorizing Official
/label ~"Container::Initial"
/cc @ironbank-notifications/cht
\ No newline at end of file
## Summary
Requesting application be updated to a newer version.
## Version Information
Current version: (State the current version of the application as you see it)
Updated version: (State the version you would like the application updated to)
Under support: (Is the updated version within the same major version of the application or is this a new major version?)
## Definition of Done
Hardening:
- [ ] Container builds successfully
- [ ] Container version has been updated in greylist file
- [ ] Branch has been merged into `development`
Justifications:
- [ ] All findings have been justified per the above documentation
- [ ] Justifications have been provided to the container hardening team
Approval Process:
- [ ] Peer review from Container Hardening Team
- [ ] Findings Approver has reviewed and approved all justifications
- [ ] Approval request has been sent to Authorizing Official
- [ ] Approval request has been processed by Authorizing Official
/label ~"Container::Update"
/cc @ironbank-notifications/updates
\ No newline at end of file
## Summary
(Summarize the bug encountered concisely)
## Steps to reproduce
(How one can reproduce the issue - this is very important)
## What is the current bug behavior?
(What actually happens)
## What is the expected correct behavior?
(What you should see instead)
## Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
## Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
## Defintion of Done
- [ ] Bug has been identified and corrected within the container
/label ~Bug
/cc @ironbank-notifications/bug
\ No newline at end of file
## Feature description
(Detailed description of the feature being requested)
## Use cases
(Detailed description of the use case for this feature)
## Benefits
(How does this benefit others)
## Requirements
(Any requirements for this feature to be enabled?)
## Links / references
(List of links or references that support this feature)
## Definition of Done
- [ ] Feature has been implemented
/label ~Feature
/cc @ironbank-notifications/feature
\ No newline at end of file
## Leadership question
(Detailed description of the question you'd like to ask the leadership team)
/label ~"Question::Leadership" ~"To Do"
/cc @ironbank-notifications/leadership
\ No newline at end of file
## Summary
Container has new findings discovered during continuous monitoring.
## Definition of Done
Justifications:
- [ ] All findings have been justified
- [ ] Justifications have been provided to the container hardening team
Approval Process:
- [ ] Findings Approver has reviewed and approved all justifications
- [ ] Approval request has been sent to Authorizing Official
- [ ] Approval request has been processed by Authorizing Official
/label ~"Container::New Findings"
/cc @ironbank-notifications/security
\ No newline at end of file
## Onboarding question
(Detailed description of the question you'd like to ask the onboarding team)
/label ~"Question::Onboarding" ~"To Do"
/cc @ironbank-notifications/onboarding
\ No newline at end of file
## Summary
(Summarize the pipeline issue encountered concisely)
## Link to failed pipeline
(Link to the failed pipeline)
## What is the current bug behavior?
(What actually happens)
## What is the expected correct behavior?
(What you should see instead)
## Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
## Definition of Done
- [ ] Pipeline failure has been resolved
/label ~Pipeline
/cc @ironbank-notifications/pipelines
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment