redteam-project / sckg Goto Github PK

View Code? Open in Web Editor NEW

38.0 7.0 16.0 56.23 MB

Security Control Knowledge Graph

License: GNU General Public License v3.0

Python 0.22% Shell 99.76% Puppet 0.01% Jinja 0.02%

information-assurance security-compliance graph graph-database infosec neo4j python

sckg's People

Contributors

Stargazers

Watchers

Forkers

emmandeb trevorbryant elavenrac gwx-oss ekmixon pombredanne dgfug swilliamx bluenevus omkarparkhe avenchen xee5ch umhau rgutwein tearfas

sckg's Issues

CMMC

I've extracted the controls in CMMC v1.02 for usability. We'll figure out what needs to be correlated from CMMC <> 800-171 <> 800-53.

https://github.com/trevorbryant/cmmc-controls

800-53 baseline impact mappings are broken

Control names appear to be empty in the generated cypher

Comment and document

Code needs to be commented.

Readme and hacking docs are incomplete.

Templates are confusing

The cypher templates are confusing and need to be made consistent

Document how to add an additional regime

Populate the hacking doc with instructions on how to add arbitrary regimes

Add 800-53A and update DoD CCI mappings

There are numerous CCIs that map to 800-53A controls. For example:

<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="AC-1.2 (i)" />

Add 800-53A to the graph and update DoD CCI mappings, noting that some use logical and descriptions like:

<reference creator="NIST" title="NIST SP 800-53A" version="1" location="http://csrc.nist.gov/publications/PubsSPs.html" index="AC-1.1 (i and ii)" />

Add a CONTRIBUTING.MD file

Add guidelines to communicate how people should contribute to project.

Reference: Setting guidelines for repository contributors

Add EDB to the graph

Map in the Exploit Database to the graph

PCI DSS unittest fails

======================================================================
FAIL: test_control_count_pci_dss (test_regime_etl.TestConfigYaml)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/jasoncallaway/PycharmProjects/sckg/tests/test_regime_etl.py", line 97, in test_control_count_pci_dss
    self.assertEquals(r[0], r[1])
AssertionError: 598 != 513

----------------------------------------------------------------------

Add CVE-to-Control mappings

Add mappings from CVEs to NIST 800-53 controls that would mitigate the vulnerability from the CVE

notification test issue

CIS CSC unittest fails

======================================================================
FAIL: test_control_count_cis_csc (test_regime_etl.TestConfigYaml)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/jasoncallaway/PycharmProjects/sckg/tests/test_regime_etl.py", line 90, in test_control_count_cis_csc
    self.assertEquals(r[0], r[1])
AssertionError: 191 != 171

----------------------------------------------------------------------

DoD SRG mappings to sectional controls are broken

DoD Cloud Computing Security Requirements sectional controls should map to impact levels, but don't.

Reference:

sckg/data/regimes/dod_srg.tsv

Line 62 in bba5ec7

 5.2.1 DoD-SRG-5.2.1-1 X X X CSPs will maintain all government data that is not physically located on DoD premises within the 50 States, the District of Columbia, and outlying areas of the US. 

match (r:regime {name: 'DoD SRG'})-[:HAS]->(b:baseline) with r, b match p = (b)-[:HAS*]->(c:control) return r, b, p

Note lack of relationships from IL4, 5, and 6 nodes. For example, given the referenced source line above, 4, 5, and 6 should map to section 5.2.1.

Need better way to skip extant regimes

The best way to quickly work on a private regime is to comment out the regimes in config.yml. But if your private regime includes a baseline that references a regime in config.yml it doesn't work.

NIST 800-171

Add 800-171 to the graph just in case we need it for CMMC

CNSSI 1253 Privacy Overlay unittest fails

======================================================================
FAIL: test_control_count_cnssi_pii (test_regime_etl.TestConfigYaml)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/jasoncallaway/PycharmProjects/sckg/tests/test_regime_etl.py", line 81, in test_control_count_cnssi_pii
    self.assertEquals(r[0], r[1])
AssertionError: 231 != 129

----------------------------------------------------------------------

redteam-project / sckg Goto Github PK

sckg's People

Contributors

Stargazers

Watchers

Forkers

sckg's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs