-
Notifications
You must be signed in to change notification settings - Fork 15
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
Onboarding Chiaka (compliance) #1700
Comments
mogul
changed the title
Checklist for Onboarding a New Compliance Team Member
Onboarding Chiaka (compliance)
Apr 4, 2022
Update this checklist so compliance also requests microsoft office |
Test comment - Chiaka Opara |
I've not added Chiaka to:
|
Since we need to set up windows, most of the development env. steps are now in cloud-gov/private#986 |
PR #1729 has updates to onboarding process for compliance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Chiaka Onboarding Checklist
✅ NOTE: Do not create this issue until the System Owner has formally authorized and requested it.
In order to get
New Person
productively contributing to the cloud.gov team,Buddy
should helpNew Person
complete a prescribed set of tasks that will bring them up to speed and get them setup with cloud.gov.Instructions
Buddy
can’t complete any of the items on their checklist personally, they are responsible for ensuring that someone with the correct access completes that item.Onboarding Checklist
Required items for all team members
These items help us fulfill security and compliance requirements (including for FedRAMP). If you get stuck, or if these requirements are confusing, ask for help from your buddy or in a cloud.gov channel.
Pre-requisites
Fulfill security and compliance requirements (including for FedRAMP) - Completed by onboarding buddy
cloud-gov
organization in GitHub, and thecloud-gov-team
team.Learn our policies and procedures
For the three trainings list at the top, your onboarding buddy will create a separate ticket to track the trainings once scheduling has been finished. This will help consolidate trainings for multiple new members to the team and prevent them from blocking progress on this onboarding ticket. Once the trainings are scheduled, they can be marked as complete here.
Getting to know cloud.gov
These items will help you come up to speed on cloud.gov and what it is, how it works, why it exists, etc. While you
should take the time to go through them, please do not try and tackle it all in one shot! It can become overwhelming
very quickly, so your onboarding buddy will walk through this list with you at a high level with you to help manage the work.
Slack channels
Your onboarding buddy will add you to these Slack channels:
#cloud-gov
- bots post announcements here#cg-billing
- private business development channel (if applicable)#cg-business
- business development (if applicable)#cg-compliance
- compliance-related information and discussion#cg-offtopic
- off-topic team sharing#cg-platform
- platform operations#cg-platform-news
- bots post platform alerts#cg-general
- program-level information and discusion#cg-support
- support requests and assistance within TTS#cg-incidents
- private channel for incident response#cg-supportstream
- notification channel from our support system, ZenDesk#cg-priv-all
- private channel for in-team discussion#cg-priv-gov
(Federal employees only) - may contain discussion of contracting-related or other private, federal-employee-only commsOnce you're added to these channels, you probably want to mute these channels until you're on support rotation:
#cg-supportstream
- notification channel from our support system, ZenDesk#cg-support
- support requests and assistance within TTS#cg-platform-news
- platform alertsCompliance-role specific items
You should already have admin rights on your machine as a part of its original setup. If for whatever reason you don't,
Please let your onboarding buddy know and they will help you request local admin rights on your GFE Mac using this justification.
Cloud Operations account management
Note: These are all contingent on completing the GSA Mandatory Cyber Security and Privacy Training first. AWS user names should be identical across accounts so that permissions can be correctly managed by Terraform.
platform-ops
team in GitHub.Your onboarding buddy will create a separate ticket tied to this one to track the AWS accounts being granted full admin access.
Additional compliance setup/review
caulking
git leak prevention by following the READMEcaulking
by runningmake audit
and pasting a screenshot as a comment on this GitHub issueInstall a development environment for cloud.gov
brew
)brew tap cloudfoundry/tap
brew install cf-cli@7
brew install openssl
cf login -a api.fr.cloud.gov --sso
cf orgs
brew install cloudfoundry/tap/bosh-cli
bosh -v
in the command linebrew install terraform
brew install awscli
brew install jq
terraform
and helper text should displayaws
and helper text should displayaws-vault
by following our directionsfly
CLIfly
binary zip for MacOS from https://concourse-ci.org//usr/local/bin/fly
so it's in your pathcd ~/Downloads
mv fly /usr/local/bin/fly
fly -h
in your command linecg-scripts
repo: rungit clone https://github.com/cloud-gov/cg-scripts.git
in your command lineThese are items that are only necessary for someone stepping into a compliance role, but you can still subscribe to the alerts and mailing lists if you're interested:
The text was updated successfully, but these errors were encountered: