UNCLASSIFIED - NO CUI

I would like to be onboarded to the dsop.io community

Initial Onboarding

-Use this template if you are a vendor/contributor looking to push your container to the DCAR.

Contributor Details

Name of vendor/contributor:

S & S Consulting Group, a Puppet Consultancy from Atlanta, GA

Containers to be added:

I plan on creating and supplying hardening code to be use in container hosts and on-container themselves.

Developer Information:

I am a sole proprietor of Puppet Consultation, training, and delivery to public and private companies nationwide. I have no intention of selling, just sharing my repos as I create them. Yes, the expectation would be one of visibility to those who may desire to reach out and engage my services, but I have no plans to actively solicit.

Additional Information

My understanding is that Puppet automation is pretty big in the government consulting space. Seeing that I am a startup, I feel I have much to offer that could be mutually beneficial, therefore I wish to create some content for share and as an example of my work, and perhaps secure some interest at a future date.

Next Steps

Once you have been granted access to the DCCSCR, you can begin the container hardening process as a contributor. A member of the Container Hardening will indicate when we have given you access to the DCCSCR.

Container Requirements

Use this template for each container you will be adding to the Iron Bank. Please view our Quickstart Guide to get started.

Contributor Responsibilities

  • Is the repo hierarchy correct?

  • Is the Dockerfile correctly defined?

  • If necessary, is the download.json properly formatted and filled out?

  • Is there a LICENSE?

  • Does the README have the necessary information?*

  • Are all findings mitigated or justified?**

  • Have you sent an email to the Approver with your justifications file attached?

Container Hardening Team Responsibilities

  • Has the submodule for this project been added to the DCCSCR repo?

  • Has the .greylist been created in the dccscr-whitelists repo?

  • Has a pipeline been created in Jenkins for this repo?

Final Approval

Assuming all of the previous steps have been taken, the final step is for the Approver to give an 'approval' status.

  • Has the Approver responded to your justifications submission, approving your container?

* If all of the requirements up to this point are met, the next step is for a member from the CHT to merge in your MR. For information regarding on next steps once your container is merged has gone through our pipeline, please visit the Iron Bank section of the reference.

**For guidance on this and the next step please visit our Whitelist Procedures.

UNCLASSIFIED - NO CUI