Skip to content
This repository has been archived by the owner on Feb 20, 2022. It is now read-only.

Controls are not being executed #191

Open
asangeethada opened this issue Oct 15, 2021 · 2 comments
Open

Controls are not being executed #191

asangeethada opened this issue Oct 15, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@asangeethada
Copy link

asangeethada commented Oct 15, 2021

Describe the bug
I followed the instructions to collect data using aws_recon and also followed the changes on this issue #78 but I am getting the following errors when i launch opencspm on my local machine

opencspm-worker-1 | Loading /app/load_dir/combined_for_load.json
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 | Warning: no EC2 loader defined for asset type: prefix_list
opencspm-worker-1 |
opencspm-worker-1 |
opencspm-worker-1 | Done loading /app/load_dir/combined_for_load.json. (66 lines)

OpenCSPM version
0.1.23

To Reproduce
Steps to reproduce the behavior:

  1. Run aws_recon
  2. Copy output.json to opencspm/assets/custom/aws (I tried both this and opencspm/assets/custom/)
  3. docker-compose up
  4. See error

Expected behavior
My ec2 information should be parsed to the controls and some controls should show as failing for example (darkbit-aws-164)

Screenshots
image

Docker information (please complete the following information):

  • Output of full docker version (not docker -v)
    Client:
    Cloud integration: 1.0.17
    Version: 20.10.8
    API version: 1.41
    Go version: go1.16.6
    Git commit: 3967b7d
    Built: Fri Jul 30 19:55:20 2021
    OS/Arch: darwin/amd64
    Context: default
    Experimental: true

Server: Docker Engine - Community
Engine:
Version: 20.10.8
API version: 1.41 (minimum version 1.12)
Go version: go1.16.6
Git commit: 75249d8
Built: Fri Jul 30 19:52:31 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.9
GitCommit: e25210fe30a0a703442421b0f60afac609f950a3
runc:
Version: 1.0.1
GitCommit: v1.0.1-0-g4144b63
docker-init:
Version: 0.19.0
GitCommit: de40ad0

  • Output of full docker-compose version (not docker-compose -v)
    Docker Compose version v2.0.0

Cloud provider (if applicable):
AWS

Additional context
I also downloaded the enterprise controls just to do a complete POC. Any help is appreciated. Thanks

@asangeethada asangeethada added the bug Something isn't working label Oct 15, 2021
@joshlarsen
Copy link
Contributor

The warnings are harmless. There are not currently any control written for prefix lists, so not loading them will have no effect.

@asangeethada
Copy link
Author

But none of the EC2 controls seem to be running against the inventory.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants