Skip to content

Commit

Permalink
polish
Browse files Browse the repository at this point in the history
  • Loading branch information
powellquiring committed Aug 15, 2023
1 parent 0fc4b78 commit 9898429
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 2 deletions.
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
# Changelog
## 1.0.7
Added one check: IBM Cloud Security Best Practices, 2.115 Ensure Databases for MongoDB version is up-to-date
## 1.0.6
Changed compliance controls to version 1.2.0 changed rule to 1.46
## 1.0.1
Expand Down
10 changes: 9 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,14 +85,22 @@ Schematics is a cloud based Infrastructure as Code runner with cloud based state

The link above should have opened a schematics workspace in the create dialog with the github repository pre-configured and terraform 1.4 selected. Change the **Workspace name**, **Resource group**, and **Location** as desired. This will be the resource group of the workspace. The resource group of the resources created will be configured in schematics. Click **Create**.

## Provision as a Deployable Architecture
## Create pricate catalog for a Deployable Architecture
In the IBM Cloud create a private catalog and then add a product to the catalog:
- Product type: Deployable architecture
- Deliver method: Terraform
- Public repository: Open the [releases](https://github.com/IBM-Cloud/nodejs-MEAN-stack/releases) and right click on the source.code.tar.gz file and paste in the string. Example: https://github.com/IBM-Cloud/nodejs-MEAN-stack/archive/refs/tags/1.0.3.tar.gz
- Variation: Standard
- Rest of the values are pretty clear

Click on the **Version** in the Version list. It will walk through a wizard where the defaults are correct, just click **Next** in all of the pages till you reach Validate version, and click **Validate**, to create a schematics workspace and resources.

After validation is complete create/configure or open the Security and Compliance and run a scan over the entire account using the **IBM Cloud Security Best Practices version 1.2.0** profile by opening the profile and click Attach in the action menu. Frequency can be set to 30 days since the first scan will be run presently and that will provide the results that are required.

Currently the scan results are failing.

## Create a Project
Create a project and then create a configuration in the project using the private catalog product version created in the previous step. Override the Code Risk Analyzer failure for the encryption of the MongoDB.

## Contribute
Please create a pull request with your desired changes.
Expand Down
2 changes: 1 addition & 1 deletion ibm_catalog.json
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@
"version": "1.2.0"
},
"names": [
"1.46"
"2.115"
]
}
]
Expand Down

0 comments on commit 9898429

Please sign in to comment.