The Automated Risk Assessment of Microservices(ARAM) is an automated CI/CD pipline that automates best security practices for 3rd party microservices. The risk assesment is done based on the researched security compliance by the OCIO team and in agreement with the AO in an effort to minimize risk while implementing best security practices.
The following will explain how to run the Jenkins automated Risk assessment using the gitlab pipeline. This pipeline will run security policy checks against an active jenkins server running in a specified environment. These checks are user in an attempt to identify the best security practices in accordance with:
- CIS benchmark
- Jenkins Security instructions
- [SANS institute][https://www.sans.org/white-papers/36872/]
The following steps need to be taken prior to running the test.
- Access to appstream
- Access to gitlab on primrosenet
- Access to the AMRA board on GDEV as a maintainer or higher
- Establish variables within gitlab project including:
BASTION - User and IP address of jump box
BASTION_PUB - Bastion public key
JENKINS - URL to Jenkins server being assessed
JENKINS_SERVER - User and IP address of Jenkins server
TOKEN - (Optional) Used for interacting with
NOTE - This may require configuration and communication with the system owner of the Jenkins instance
The following instructions will guide a user to running a Security assessment against a configured Jenkins server
- Browser- Navigate to app stream
- Appstream- Open a browser and click the gitlab icon
- Appstream- Sign in to gitlab
- Appstream- Navigate to gitlab.primrosenet.net/ISRM/aram/-/pipelines/new
- Appstream- Click
Run Pipeline
button - Appstream- Wait 2-4 minutes for the jobs to run
- Appstream- Evaluate Jobs that passed or failed
- Appstream- Click a job
- Appstream- Download artifacts (passed or failed) and save to Downloads folder
- Appstream- Open notepad++ on appstream
- Appstream- Click
File -> open -> Downloads
- Appstream- Right click the
artifacts
and selectExtract All...
- Appstream- Click
Extract
- Appstream- Click
results
folder and then click the text file - Appstream- Verify information
For failures reference the Failed jobs section
- Browser- Reference Jenkins jobs
- Browser- Step through the Manual Assessment method of any jobs that may have failed
- Browser- Verify solution and create issues as needed