dev-sec / dev-sec/dev-sec.github.io

data structure of baseline.yml

Open
#29 0 comments 0 reactions 2 assignees View on GitHub

@artem-sidorenko is already working on this.

Since Dec 19, 2018.

Dominant language
SCSS
Stars
22
Forks
15
Avg merge
4h 41m
Merged PRs (30d)
1

Description

@mtollick and @aaronlippold were looking at streamlining some of the upkeep on the site

In reviewing the https://github.com/dev-sec/dev-sec.github.io/blob/src/data/baselines.yml file it seems that we sould really have a structure like:

This would allow us to create a more standard approach on auto processing this and looping for rebuilding source data as we need to.

baselines:
  - name: linux
     id: linux-baseline
     type: os|app|ops|comp|net|plat
     links:
       - name: InSpec Profile
         url: https://github.com/dev-sec/linux-baseline
         icon: icon-github-circled
       - name: Ansible Remediation Role
         url: https://github.com/dev-sec/ansible-os-hardening
         icon: icon-github-circled
       - name: Chef Remediation Cookbook
         url: https://github.com/dev-sec/chef-os-hardening
         icon: icon-github-circled
       - name: Puppet Remediation Module
         url: https://github.com/hardening-io/puppet-os-hardening
         icon: icon-github-circled
  - name: ssh
     ...

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.