Comments (5)
Right...but doesn't a control being listed in the certification make it implicitly "required"? I'm not understanding why any new fields would be required in the YAML.
https://github.com/opencontrol/schemas#certifications
from compliance-masonry.
CM can specify and consume RequiredControls
Mind explaining this? @jcscottiii @ctro and I saw that added to the schema in #112 but weren't sure why it actually needs to be present in the YAML. What constitutes a non-required control?
from compliance-masonry.
I think that these requirements came from Gabe, specifically "specify and consume Required Controls".
This is why the one commit I made to gap analysis added that YAML. Gabe envisioned adding all "required" controls to the project's yaml. Then, you can check for the existence of those requiredControls in your actual documentation.
Is this because projects don't want/need to implement ALL of the controls for some Certification?? In this case diffing against all controls wouldn't be too useful.
I am also unsure of what makes a control required or not.
Maybe defining your list of requiredControls is the first step of using CM. How many controls are usually required for a project though? 10? 30? 400?
from compliance-masonry.
All good questions. Maybe this is related to some controls being partially fulfilled by the different layers, e.g. that the platform itself has monitoring, but that is not the same thing as an application having monitoring. @mogul @dlapiduz Any guesses?
from compliance-masonry.
The required controls are determined by the baseline you're shooting for. So if you're trying to document a FISMA Moderate system, that will imply a certain set of controls need to be satisfied, which means that you should have something showing up under each of them in your assembled docs. The gap report should say "To get FISMA Moderate, there should be something here, here, and here". If it were FISMA Low, it'd be a smaller set. If it was PCI or HIPAA, it would be a different set. Make sense?
from compliance-masonry.
Related Issues (20)
- masonry release of latest (v1.2.0?) HOT 1
- General: leveraging github actions for building, testing, releasing HOT 1
- General: leverage dependabot HOT 1
- Consider packaging with e.g. (docker) Drydock pattern
- References specific to a component's "satisfies" are not rendered
- Could 'covered_by' in a control response 'cover' more than 'verifications'?
- Replace circleci with github actions
- Replace travis with github actions
- Include provenance information in generated content (may be gitbook / markdown issue?)
- "verification" for Image type are not included as part of masonry docs gitbook generation
- Consider replacing/enhancing "dependencies" retrieval mechanisms with vendoring/library, vendir
- Consider enhancing "dependencies" to support local filesystem references HOT 2
- Splitting "component" contexts across multiple yaml files
- Enhance error reporting/message HOT 2
- Readdress race condition on integration tests
- Dependabot performing go mod vendor now-- nifty HOT 2
- "Covered By" appears to lack newline, is directly appended to previous section
- Publish 1.1.6 to docker hub
- runtime: bsdthread_register error HOT 2
- Documentation Creating
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from compliance-masonry.