From 77955ea0cbc8eea7f5411e75f3e103acd4ef701f Mon Sep 17 00:00:00 2001 From: Joshua Eason Date: Tue, 6 Oct 2020 14:10:29 +0000 Subject: [PATCH 1/8] Issue templates --- .gitlab/CODEOWNERS | 7 ++++ .../issue_templates/Archive Application.md | 17 +++++++++ .gitlab/issue_templates/Bug.md | 35 +++++++++++++++++++ .gitlab/issue_templates/Feature Request.md | 29 +++++++++++++++ .../issue_templates/Leadership Question.md | 7 ++++ .../issue_templates/Onboarding Question.md | 7 ++++ .gitlab/issue_templates/Pipeline Failure.md | 29 +++++++++++++++ .gitlab/issue_templates/Update Application.md | 19 ++++++++++ 8 files changed, 150 insertions(+) create mode 100644 .gitlab/CODEOWNERS create mode 100644 .gitlab/issue_templates/Archive Application.md create mode 100644 .gitlab/issue_templates/Bug.md create mode 100644 .gitlab/issue_templates/Feature Request.md create mode 100644 .gitlab/issue_templates/Leadership Question.md create mode 100644 .gitlab/issue_templates/Onboarding Question.md create mode 100644 .gitlab/issue_templates/Pipeline Failure.md create mode 100644 .gitlab/issue_templates/Update Application.md diff --git a/.gitlab/CODEOWNERS b/.gitlab/CODEOWNERS new file mode 100644 index 0000000..11d201d --- /dev/null +++ b/.gitlab/CODEOWNERS @@ -0,0 +1,7 @@ +[Pipelines] +.gitlab-ci.yml @ironbank-notifications/cht +.gitlab-ci.yaml @ironbank-notifications/cht +Jenkinsfile + +[Gitlab Configuration Files] +.gitlab/* @ironbank-notifications/cht \ No newline at end of file diff --git a/.gitlab/issue_templates/Archive Application.md b/.gitlab/issue_templates/Archive Application.md new file mode 100644 index 0000000..f6fb3df --- /dev/null +++ b/.gitlab/issue_templates/Archive Application.md @@ -0,0 +1,17 @@ +## 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) + + + + +/label ~archive +/cc @ironbank-notifications/archive \ No newline at end of file diff --git a/.gitlab/issue_templates/Bug.md b/.gitlab/issue_templates/Bug.md new file mode 100644 index 0000000..20fcdb7 --- /dev/null +++ b/.gitlab/issue_templates/Bug.md @@ -0,0 +1,35 @@ +## 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) + + + + +/label ~bug +/cc @ironbank-notifications/bug \ No newline at end of file diff --git a/.gitlab/issue_templates/Feature Request.md b/.gitlab/issue_templates/Feature Request.md new file mode 100644 index 0000000..b13cc8c --- /dev/null +++ b/.gitlab/issue_templates/Feature Request.md @@ -0,0 +1,29 @@ +## 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) + + + +/label ~feature +/cc @ironbank-notifications/feature \ No newline at end of file diff --git a/.gitlab/issue_templates/Leadership Question.md b/.gitlab/issue_templates/Leadership Question.md new file mode 100644 index 0000000..0d84df2 --- /dev/null +++ b/.gitlab/issue_templates/Leadership Question.md @@ -0,0 +1,7 @@ +## Leadership question + +(Detailed description of the question you'd like to ask the leadership team) + + +/label ~leadership +/cc @ironbank-notifications/leadership \ No newline at end of file diff --git a/.gitlab/issue_templates/Onboarding Question.md b/.gitlab/issue_templates/Onboarding Question.md new file mode 100644 index 0000000..025ae1d --- /dev/null +++ b/.gitlab/issue_templates/Onboarding Question.md @@ -0,0 +1,7 @@ +## Onboarding question + +(Detailed description of the question you'd like to ask the onboarding team) + + +/label ~onboarding +/cc @ironbank-notifications/onboarding \ No newline at end of file diff --git a/.gitlab/issue_templates/Pipeline Failure.md b/.gitlab/issue_templates/Pipeline Failure.md new file mode 100644 index 0000000..b9ce91b --- /dev/null +++ b/.gitlab/issue_templates/Pipeline Failure.md @@ -0,0 +1,29 @@ +## 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) + + + + +/label ~pipeline ~bug +/cc @ironbank-notifications/pipelines \ No newline at end of file diff --git a/.gitlab/issue_templates/Update Application.md b/.gitlab/issue_templates/Update Application.md new file mode 100644 index 0000000..7a06f3c --- /dev/null +++ b/.gitlab/issue_templates/Update Application.md @@ -0,0 +1,19 @@ +# 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?) + + + + +/label ~update +/cc @ironbank-notifications/updates \ No newline at end of file -- GitLab From 392b2883198f30394f90e51f93afbf80becccf4e Mon Sep 17 00:00:00 2001 From: Joshua Eason Date: Tue, 6 Oct 2020 17:22:23 +0000 Subject: [PATCH 2/8] Issue templates --- .gitlab/CODEOWNERS | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.gitlab/CODEOWNERS b/.gitlab/CODEOWNERS index 11d201d..64a2c68 100644 --- a/.gitlab/CODEOWNERS +++ b/.gitlab/CODEOWNERS @@ -1,7 +1,6 @@ [Pipelines] .gitlab-ci.yml @ironbank-notifications/cht .gitlab-ci.yaml @ironbank-notifications/cht -Jenkinsfile [Gitlab Configuration Files] -.gitlab/* @ironbank-notifications/cht \ No newline at end of file +.gitlab/* @ironbank-notifications/cht -- GitLab From aad1cd0e65e45bc5ac223d189dffa76f98252c9c Mon Sep 17 00:00:00 2001 From: Joshua Eason Date: Fri, 9 Oct 2020 00:12:09 +0000 Subject: [PATCH 3/8] Issue templates --- .gitlab/issue_templates/Access Request.md | 16 +++++++++ .../issue_templates/Application - Archive.md | 21 +++++++++++ .../issue_templates/Application - Initial.md | 32 +++++++++++++++++ .../issue_templates/Application - Update.md | 35 +++++++++++++++++++ .gitlab/issue_templates/Bug.md | 4 ++- .gitlab/issue_templates/Feature Request.md | 5 ++- .../issue_templates/Leadership Question.md | 2 +- .gitlab/issue_templates/New Findings.md | 20 +++++++++++ .../issue_templates/Onboarding Question.md | 2 +- .gitlab/issue_templates/Pipeline Failure.md | 4 ++- 10 files changed, 136 insertions(+), 5 deletions(-) create mode 100644 .gitlab/issue_templates/Access Request.md create mode 100644 .gitlab/issue_templates/Application - Archive.md create mode 100644 .gitlab/issue_templates/Application - Initial.md create mode 100644 .gitlab/issue_templates/Application - Update.md create mode 100644 .gitlab/issue_templates/New Findings.md diff --git a/.gitlab/issue_templates/Access Request.md b/.gitlab/issue_templates/Access Request.md new file mode 100644 index 0000000..1a7b224 --- /dev/null +++ b/.gitlab/issue_templates/Access Request.md @@ -0,0 +1,16 @@ +## 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 diff --git a/.gitlab/issue_templates/Application - Archive.md b/.gitlab/issue_templates/Application - Archive.md new file mode 100644 index 0000000..9f3b5fe --- /dev/null +++ b/.gitlab/issue_templates/Application - Archive.md @@ -0,0 +1,21 @@ +## 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 diff --git a/.gitlab/issue_templates/Application - Initial.md b/.gitlab/issue_templates/Application - Initial.md new file mode 100644 index 0000000..6594a05 --- /dev/null +++ b/.gitlab/issue_templates/Application - Initial.md @@ -0,0 +1,32 @@ +## 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 diff --git a/.gitlab/issue_templates/Application - Update.md b/.gitlab/issue_templates/Application - Update.md new file mode 100644 index 0000000..caebb3e --- /dev/null +++ b/.gitlab/issue_templates/Application - Update.md @@ -0,0 +1,35 @@ +## 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 diff --git a/.gitlab/issue_templates/Bug.md b/.gitlab/issue_templates/Bug.md index 20fcdb7..1427a0c 100644 --- a/.gitlab/issue_templates/Bug.md +++ b/.gitlab/issue_templates/Bug.md @@ -29,7 +29,9 @@ logs, and code as it's very hard to read otherwise.) (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 +/label ~Bug /cc @ironbank-notifications/bug \ No newline at end of file diff --git a/.gitlab/issue_templates/Feature Request.md b/.gitlab/issue_templates/Feature Request.md index b13cc8c..a0e2f19 100644 --- a/.gitlab/issue_templates/Feature Request.md +++ b/.gitlab/issue_templates/Feature Request.md @@ -24,6 +24,9 @@ (List of links or references that support this feature) +## Definition of Done +- [ ] Feature has been implemented -/label ~feature + +/label ~Feature /cc @ironbank-notifications/feature \ No newline at end of file diff --git a/.gitlab/issue_templates/Leadership Question.md b/.gitlab/issue_templates/Leadership Question.md index 0d84df2..4674f82 100644 --- a/.gitlab/issue_templates/Leadership Question.md +++ b/.gitlab/issue_templates/Leadership Question.md @@ -3,5 +3,5 @@ (Detailed description of the question you'd like to ask the leadership team) -/label ~leadership +/label ~"Question::Leadership" ~"To Do" /cc @ironbank-notifications/leadership \ No newline at end of file diff --git a/.gitlab/issue_templates/New Findings.md b/.gitlab/issue_templates/New Findings.md new file mode 100644 index 0000000..068d029 --- /dev/null +++ b/.gitlab/issue_templates/New Findings.md @@ -0,0 +1,20 @@ +## 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 diff --git a/.gitlab/issue_templates/Onboarding Question.md b/.gitlab/issue_templates/Onboarding Question.md index 025ae1d..77dea11 100644 --- a/.gitlab/issue_templates/Onboarding Question.md +++ b/.gitlab/issue_templates/Onboarding Question.md @@ -3,5 +3,5 @@ (Detailed description of the question you'd like to ask the onboarding team) -/label ~onboarding +/label ~"Question::Onboarding" ~"To Do" /cc @ironbank-notifications/onboarding \ No newline at end of file diff --git a/.gitlab/issue_templates/Pipeline Failure.md b/.gitlab/issue_templates/Pipeline Failure.md index b9ce91b..28b82a9 100644 --- a/.gitlab/issue_templates/Pipeline Failure.md +++ b/.gitlab/issue_templates/Pipeline Failure.md @@ -23,7 +23,9 @@ (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 ~bug +/label ~Pipeline /cc @ironbank-notifications/pipelines \ No newline at end of file -- GitLab From a2f9008ae4c4f9fba2ecc79a7b41adc7a85790d4 Mon Sep 17 00:00:00 2001 From: Joshua Eason Date: Thu, 8 Oct 2020 18:14:15 -0600 Subject: [PATCH 4/8] Removing duplicate issues --- .../issue_templates/Archive Application.md | 17 ----------------- .gitlab/issue_templates/Update Application.md | 19 ------------------- 2 files changed, 36 deletions(-) delete mode 100644 .gitlab/issue_templates/Archive Application.md delete mode 100644 .gitlab/issue_templates/Update Application.md diff --git a/.gitlab/issue_templates/Archive Application.md b/.gitlab/issue_templates/Archive Application.md deleted file mode 100644 index f6fb3df..0000000 --- a/.gitlab/issue_templates/Archive Application.md +++ /dev/null @@ -1,17 +0,0 @@ -## 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) - - - - -/label ~archive -/cc @ironbank-notifications/archive \ No newline at end of file diff --git a/.gitlab/issue_templates/Update Application.md b/.gitlab/issue_templates/Update Application.md deleted file mode 100644 index 7a06f3c..0000000 --- a/.gitlab/issue_templates/Update Application.md +++ /dev/null @@ -1,19 +0,0 @@ -# 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?) - - - - -/label ~update -/cc @ironbank-notifications/updates \ No newline at end of file -- GitLab From 4e9a6428b2907025e5f667293a415632f7a3dc90 Mon Sep 17 00:00:00 2001 From: Joshua Eason Date: Mon, 26 Oct 2020 14:40:37 +0000 Subject: [PATCH 5/8] Development --- .gitlab/issue_templates/Application - Archive.md | 3 +-- .gitlab/issue_templates/Application - Initial.md | 3 +-- .gitlab/issue_templates/Application - Update.md | 3 +-- .gitlab/issue_templates/Bug.md | 3 +-- .gitlab/issue_templates/Feature Request.md | 3 +-- .gitlab/issue_templates/New Findings.md | 3 +-- .gitlab/issue_templates/Pipeline Failure.md | 3 +-- README.md | 2 +- 8 files changed, 8 insertions(+), 15 deletions(-) diff --git a/.gitlab/issue_templates/Application - Archive.md b/.gitlab/issue_templates/Application - Archive.md index 9f3b5fe..a558faa 100644 --- a/.gitlab/issue_templates/Application - Archive.md +++ b/.gitlab/issue_templates/Application - Archive.md @@ -17,5 +17,4 @@ Requesting this application be archived due to one of the following reasons: - [ ] Iron Bank frontend no longer lists application as available or approved -/label ~"Container::Archive" -/cc @ironbank-notifications/archive \ No newline at end of file +/label ~"Container::Archive" \ No newline at end of file diff --git a/.gitlab/issue_templates/Application - Initial.md b/.gitlab/issue_templates/Application - Initial.md index 6594a05..b7acebd 100644 --- a/.gitlab/issue_templates/Application - Initial.md +++ b/.gitlab/issue_templates/Application - Initial.md @@ -28,5 +28,4 @@ Approval Process (container hardening team processes): -/label ~"Container::Initial" -/cc @ironbank-notifications/cht \ No newline at end of file +/label ~"Container::Initial" \ No newline at end of file diff --git a/.gitlab/issue_templates/Application - Update.md b/.gitlab/issue_templates/Application - Update.md index caebb3e..d95cb35 100644 --- a/.gitlab/issue_templates/Application - Update.md +++ b/.gitlab/issue_templates/Application - Update.md @@ -31,5 +31,4 @@ Approval Process: -/label ~"Container::Update" -/cc @ironbank-notifications/updates \ No newline at end of file +/label ~"Container::Update" \ No newline at end of file diff --git a/.gitlab/issue_templates/Bug.md b/.gitlab/issue_templates/Bug.md index 1427a0c..2030c24 100644 --- a/.gitlab/issue_templates/Bug.md +++ b/.gitlab/issue_templates/Bug.md @@ -33,5 +33,4 @@ logs, and code as it's very hard to read otherwise.) - [ ] Bug has been identified and corrected within the container -/label ~Bug -/cc @ironbank-notifications/bug \ No newline at end of file +/label ~Bug \ No newline at end of file diff --git a/.gitlab/issue_templates/Feature Request.md b/.gitlab/issue_templates/Feature Request.md index a0e2f19..94aea9a 100644 --- a/.gitlab/issue_templates/Feature Request.md +++ b/.gitlab/issue_templates/Feature Request.md @@ -28,5 +28,4 @@ - [ ] Feature has been implemented -/label ~Feature -/cc @ironbank-notifications/feature \ No newline at end of file +/label ~Feature \ No newline at end of file diff --git a/.gitlab/issue_templates/New Findings.md b/.gitlab/issue_templates/New Findings.md index 068d029..1fd613d 100644 --- a/.gitlab/issue_templates/New Findings.md +++ b/.gitlab/issue_templates/New Findings.md @@ -16,5 +16,4 @@ Approval Process: -/label ~"Container::New Findings" -/cc @ironbank-notifications/security \ No newline at end of file +/label ~"Container::New Findings" \ No newline at end of file diff --git a/.gitlab/issue_templates/Pipeline Failure.md b/.gitlab/issue_templates/Pipeline Failure.md index 28b82a9..dd6ab98 100644 --- a/.gitlab/issue_templates/Pipeline Failure.md +++ b/.gitlab/issue_templates/Pipeline Failure.md @@ -27,5 +27,4 @@ - [ ] Pipeline failure has been resolved -/label ~Pipeline -/cc @ironbank-notifications/pipelines \ No newline at end of file +/label ~Pipeline \ No newline at end of file diff --git a/README.md b/README.md index f2a2b88..5dc6fa6 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,3 @@ -# master-project-template +# Project template for all Iron Bank container repositories. \ No newline at end of file -- GitLab From 0ac6e5a19664140eab6f016c390b8d8c708726f4 Mon Sep 17 00:00:00 2001 From: Joshua Eason Date: Wed, 17 Mar 2021 21:01:23 -0600 Subject: [PATCH 6/8] Project template: file templates --- .gitlab/issue_templates/Access Request.md | 3 ++ .../issue_templates/Application - Archive.md | 3 ++ .../issue_templates/Application - Initial.md | 54 +++++++++++++++++-- .../issue_templates/Application - Update.md | 52 +++++++++++++++++- .gitlab/issue_templates/Bug.md | 5 ++ .gitlab/issue_templates/Feature Request.md | 5 ++ .../issue_templates/Leadership Question.md | 5 ++ .gitlab/issue_templates/New Findings.md | 8 +++ .../issue_templates/Onboarding Question.md | 5 ++ .gitlab/issue_templates/Pipeline Failure.md | 6 +++ 10 files changed, 139 insertions(+), 7 deletions(-) diff --git a/.gitlab/issue_templates/Access Request.md b/.gitlab/issue_templates/Access Request.md index 1a7b224..2e3e8b7 100644 --- a/.gitlab/issue_templates/Access Request.md +++ b/.gitlab/issue_templates/Access Request.md @@ -13,4 +13,7 @@ The access level should be: - [ ] All accounts have been provided the necessary accesses + + + /label ~"Access" ~"To Do" \ No newline at end of file diff --git a/.gitlab/issue_templates/Application - Archive.md b/.gitlab/issue_templates/Application - Archive.md index a558faa..0304276 100644 --- a/.gitlab/issue_templates/Application - Archive.md +++ b/.gitlab/issue_templates/Application - Archive.md @@ -17,4 +17,7 @@ Requesting this application be archived due to one of the following reasons: - [ ] Iron Bank frontend no longer lists application as available or approved + + + /label ~"Container::Archive" \ No newline at end of file diff --git a/.gitlab/issue_templates/Application - Initial.md b/.gitlab/issue_templates/Application - Initial.md index b7acebd..7ddab91 100644 --- a/.gitlab/issue_templates/Application - Initial.md +++ b/.gitlab/issue_templates/Application - Initial.md @@ -7,25 +7,69 @@ Requesting application to be hardened. This is only for initial hardening of a c 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?) +## Communication + +All communication should occur through this issue. This ensures that all information is documented in a centralized location and also ensures that all of the assignees are notified of updates. It is imperative that all required parties are listed as assignees of this issue and that individuals are not removed. Please do not remove anyone from the assignee list. + +If you need to contact the Container Hardening team, please identify your assigned point of contact. You can find your point of contact by: +1. They should be listed as an assignee on this ticket +2. They should be listed in the `hardening_manifest.yaml` file under the `maintainers` section with a field of `cht_member: true` + +If you have no assignee, feel free to tag Container Hardening leadership in your issue by commenting on this issue with your questions/concerns and then add `/cc @ironbank-notifications/leadership`. Gitlab will automatically notify all Container Hardening leadership to look at this issue and respond. + + +## Responsibilities + +If this application is owned by a Contributor or Vendor (identifed as `Owner::Contributor` and `Owner::Vendor` respectively), then it is your responsibility to drive this issue through completion. This means that the Container Hardening team is not here to help push any deadlines/timeframes you may have with other customers or DoD agencies. If you have issues with the activity, you may notify Container Hardening leadership above. Do not change the ownership labels. ## Definition of Done + Hardening: -- [ ] Container builds successfully -- [ ] Greylist file has been created (requires a member from container hardening) +- [ ] Hardening manifest is created and adheres to the schema (https://repo1.dsop.io/ironbank-tools/ironbank-pipeline/-/blob/master/schema/hardening_manifest.schema.json) +- [ ] Container builds successfully through the Gitlab CI pipeline - [ ] Branch has been merged into `development` +- [ ] Project is configured for automatic renovate updates (if possible) Justifications: - [ ] All findings have been justified per the above documentation -- [ ] Justifications have been provided to the container hardening team +- [ ] Justifications have been attached to this issue +- [ ] Apply the label `Approval` to indicate this container is ready for the approval phase + +Note: The justifications must be provided in a timely fashion. Failure to do so could result in new findings being identified which may start this process over. -Approval Process (container hardening team processes): +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 +Note: If the above approval process is kicked back for any reason, the `Approval` label will be removed and the issue will be sent back to `Open`. Any comments will be listed in this issue for you to address. Once they have been addressed, you may re-add the `Approval` label. + +## Post Approval + +### Continuous Monitoring + +Once a container is approved, the `Approved` label will be applied to this issue and it will be closed. You will be able to find your applications on http://ironbank.dsop.io and https://registry1.dsop.io. + +In addition to the above, your application will now be subscribed to continuous monitoring. This means that any new findings discovered as part of this will need justifications. To satisfy this process, any new findings will trigger a new Gitlab issue in this project with the label `Container::New Findings`. All members listed in the `maintainers` section of the `hardening_manifest.yaml` file will automatically be assigned. It is your responsibility as a Contributor or Vendor to monitor for this and provide justifications in a timely fashion. This newly created issue will have all the instructions necessary to complete the process. Failure to provide justifications could result in the revocation of the application's approval status. + +### Updates + +It is imperative that application updates be submitted as quickly as possible. We do not want applications to become stale. To help with this process, Ironbank recommends using a tool called [Renovate](https://github.com/renovatebot/renovate). This requires a `renovate.json` file to be placed in your project and can automate the creation of issues and merge requests. + +If not using Renovate, it will be up to you as a Contributor or Vendor to keep this image up-to-date at all times. When you wish to submit an application update, you must create a new issue in this project using the `Application - Update` template and associate it with the corresponding merge request. If you submit a merge request alone, work will not proceed until a related issue is created. These issues are tracked using the label `Container::Update`. + +Additionally, it is imperative that all updates must be followed through to completion. Simply submitting an application update but not following through on justifications and approvals does not suffice and risk your application's approval status being revoked. + +### Bugs + +Occassionally, users may file bug reports for your application. It is your responsibility to monitor for these since they are created inside your project repository. Assignees will automatically be populated by the `members` section of the `hardening_manifest.yaml` file and will have the label `Bug`. + + + + + /label ~"Container::Initial" \ No newline at end of file diff --git a/.gitlab/issue_templates/Application - Update.md b/.gitlab/issue_templates/Application - Update.md index d95cb35..569e75d 100644 --- a/.gitlab/issue_templates/Application - Update.md +++ b/.gitlab/issue_templates/Application - Update.md @@ -13,15 +13,38 @@ 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?) +## Communication + +All communication should occur through this issue. This ensures that all information is documented in a centralized location and also ensures that all of the assignees are notified of updates. It is imperative that all required parties are listed as assignees of this issue and that individuals are not removed. Please do not remove anyone from the assignee list. + +If you need to contact the Container Hardening team, please identify your assigned point of contact. You can find your point of contact by: +1. They should be listed as an assignee on this ticket +2. They should be listed in the `hardening_manifest.yaml` file under the `maintainers` section with a field of `cht_member: true` + +If you have no assignee, feel free to tag Container Hardening leadership in your issue by commenting on this issue with your questions/concerns and then add `/cc @ironbank-notifications/leadership`. Gitlab will automatically notify all Container Hardening leadership to look at this issue and respond. + + +## Responsibilities + +If this application is owned by a Contributor or Vendor (identifed as `Owner::Contributor` and `Owner::Vendor` respectively), then it is your responsibility to drive this issue through completion. This means that the Container Hardening team is not here to help push any deadlines/timeframes you may have with other customers or DoD agencies. If you have issues with the activity, you may notify Container Hardening leadership above. Do not change the ownership labels. + + ## Definition of Done Hardening: -- [ ] Container builds successfully -- [ ] Container version has been updated in greylist file +- [ ] Hardening manifest has been updated and adheres to the schema (https://repo1.dsop.io/ironbank-tools/ironbank-pipeline/-/blob/master/schema/hardening_manifest.schema.json) +- [ ] Container builds successfully throughthe Gitlab CI pipeline - [ ] Branch has been merged into `development` +- [ ] Project is configured for automatic renovate updates (if possible) + +No new findings: +- [ ] There are no new findings in this update. Skip the Justifications and Approval Process steps and apply the label `Approval` Justifications: - [ ] All findings have been justified per the above documentation - [ ] Justifications have been provided to the container hardening team +- [ ] Skip the Justifications and Approval Process steps and apply the label `Approval` + +Note: The justifications must be provided in a timely fashion. Failure to do so could result in new findings being identified which may start this process over. Approval Process: - [ ] Peer review from Container Hardening Team @@ -29,6 +52,31 @@ Approval Process: - [ ] Approval request has been sent to Authorizing Official - [ ] Approval request has been processed by Authorizing Official +Note: If the above approval process is kicked back for any reason, the `Approval` label will be removed and the issue will be sent back to `Open`. Any comments will be listed in this issue for you to address. Once they have been addressed, you may re-add the `Approval` label. + + +## Post Approval + +### Continuous Monitoring + +Once a container is approved, the `Approved` label will be applied to this issue and it will be closed. You will be able to find your applications on http://ironbank.dsop.io and https://registry1.dsop.io. + +In addition to the above, your application will now be subscribed to continuous monitoring. This means that any new findings discovered as part of this will need justifications. To satisfy this process, any new findings will trigger a new Gitlab issue in this project with the label `Container::New Findings`. All members listed in the `maintainers` section of the `hardening_manifest.yaml` file will automatically be assigned. It is your responsibility as a Contributor or Vendor to monitor for this and provide justifications in a timely fashion. This newly created issue will have all the instructions necessary to complete the process. Failure to provide justifications could result in the revocation of the application's approval status. + +### Updates + +It is imperative that application updates be submitted as quickly as possible. We do not want applications to become stale. To help with this process, Ironbank recommends using a tool called [Renovate](https://github.com/renovatebot/renovate). This requires a `renovate.json` file to be placed in your project and can automate the creation of issues and merge requests. + +If not using Renovate, it will be up to you as a Contributor or Vendor to keep this image up-to-date at all times. When you wish to submit an application update, you must create a new issue in this project using the `Application - Update` template and associate it with the corresponding merge request. If you submit a merge request alone, work will not proceed until a related issue is created. These issues are tracked using the label `Container::Update`. + +Additionally, it is imperative that all updates must be followed through to completion. Simply submitting an application update but not following through on justifications and approvals does not suffice and risk your application's approval status being revoked. + +### Bugs + +Occassionally, users may file bug reports for your application. It is your responsibility to monitor for these since they are created inside your project repository. Assignees will automatically be populated by the `members` section of the `hardening_manifest.yaml` file and will have the label `Bug`. + + + /label ~"Container::Update" \ No newline at end of file diff --git a/.gitlab/issue_templates/Bug.md b/.gitlab/issue_templates/Bug.md index 2030c24..069eaf0 100644 --- a/.gitlab/issue_templates/Bug.md +++ b/.gitlab/issue_templates/Bug.md @@ -33,4 +33,9 @@ logs, and code as it's very hard to read otherwise.) - [ ] Bug has been identified and corrected within the container + + + + + /label ~Bug \ No newline at end of file diff --git a/.gitlab/issue_templates/Feature Request.md b/.gitlab/issue_templates/Feature Request.md index 94aea9a..aad0671 100644 --- a/.gitlab/issue_templates/Feature Request.md +++ b/.gitlab/issue_templates/Feature Request.md @@ -28,4 +28,9 @@ - [ ] Feature has been implemented + + + + + /label ~Feature \ No newline at end of file diff --git a/.gitlab/issue_templates/Leadership Question.md b/.gitlab/issue_templates/Leadership Question.md index 4674f82..b2cf9e5 100644 --- a/.gitlab/issue_templates/Leadership Question.md +++ b/.gitlab/issue_templates/Leadership Question.md @@ -3,5 +3,10 @@ (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 diff --git a/.gitlab/issue_templates/New Findings.md b/.gitlab/issue_templates/New Findings.md index 1fd613d..867f832 100644 --- a/.gitlab/issue_templates/New Findings.md +++ b/.gitlab/issue_templates/New Findings.md @@ -8,12 +8,20 @@ Container has new findings discovered during continuous monitoring. Justifications: - [ ] All findings have been justified - [ ] Justifications have been provided to the container hardening team +- [ ] `Approval` label has been applied + +Note: The justifications must be provided in a timely fashion. Failure to do so could result in new findings being identified which may start this process over. 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 +Note: If the above approval process is kicked back for any reason, the `Approval` label will be removed and the issue will be sent back to `Open`. Any comments will be listed in this issue for you to address. Once they have been addressed, you may re-add the `Approval` label. + + + + /label ~"Container::New Findings" \ No newline at end of file diff --git a/.gitlab/issue_templates/Onboarding Question.md b/.gitlab/issue_templates/Onboarding Question.md index 77dea11..ae8011e 100644 --- a/.gitlab/issue_templates/Onboarding Question.md +++ b/.gitlab/issue_templates/Onboarding Question.md @@ -3,5 +3,10 @@ (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 diff --git a/.gitlab/issue_templates/Pipeline Failure.md b/.gitlab/issue_templates/Pipeline Failure.md index dd6ab98..36aa982 100644 --- a/.gitlab/issue_templates/Pipeline Failure.md +++ b/.gitlab/issue_templates/Pipeline Failure.md @@ -27,4 +27,10 @@ - [ ] Pipeline failure has been resolved + + + + + + /label ~Pipeline \ No newline at end of file -- GitLab From 1057accfe6141ec5ddd5bfa7cb5b505ebb15b9ca Mon Sep 17 00:00:00 2001 From: Al Fontaine Date: Thu, 26 Aug 2021 18:01:42 +0000 Subject: [PATCH 7/8] Update README.md --- README.md | 36 ++++++++++++++++++++++++++++++++++-- 1 file changed, 34 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5dc6fa6..6f22199 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,35 @@ -# +## CodeSonar 6.1p0 + +This is a default image that provides the CodeSonar Hub service. Data volumes can +be mounted such that data persists. A license from GrammaTech is required to be +able to use the hub and provide scans. Contact sales@grammatech.com for access +to a license. + +## Build the Image +Build the image using the standard + `docker build -t codesonar-hub .` + +## Running the Container +Suggested use is to run the container using: + +`docker volume create hub` + +`docker network create --driver bridge net ` + +`docker run -d --name hub -p 8080:7340 -v hub:/home/codesonar/hub --network net codesonar-hub` + +This will put all data in the hub volume and route localhost:8080 to the hub and +connect the container to network net such that scanners can connect to it. + + +## Shutdown +Recommended to shutdown the container through +`http://[host]:[port]/command/shutdown` before terminating the container + +## Resources +CPU Min/Recommended 2/8+
+RAM Min/Recommended/Max 2G/8G/Unlimited + +## Ports +Application is using port 7340 -Project template for all Iron Bank container repositories. \ No newline at end of file -- GitLab From 89c71ff5bf299255ad2b370b67a9ab6a3bea7860 Mon Sep 17 00:00:00 2001 From: Mark Hermeling Date: Sun, 29 Aug 2021 02:59:59 +0000 Subject: [PATCH 8/8] Remove VOLUME statement. --- Dockerfile | 1 - 1 file changed, 1 deletion(-) diff --git a/Dockerfile b/Dockerfile index 9523317..9a6f0d4 100644 --- a/Dockerfile +++ b/Dockerfile @@ -72,7 +72,6 @@ RUN ln -s /usr/lib64/libnsl.so.2 /usr/lib64/libnsl.so.1 -VOLUME [ /home/codesonar ] #HEALTHCHECK --interval=30s --timeout=30s --start-period=180s --retries=3 CMD /opt/codesonar-health-check.sh -- GitLab