You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+49-17Lines changed: 49 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,11 @@
1
1
# scsctl
2
+
2
3
> We are continuously adding the listed features
3
4
4
5
CLI/CI Tool for Automating Vulnerability Management for Enhancing Software Supply Chain Security Measures.
5
6
6
7
### Features
8
+
7
9
- Integration with other Tools & Platforms:
8
10
- Trivy
9
11
- Grype
@@ -24,8 +26,8 @@ CLI/CI Tool for Automating Vulnerability Management for Enhancing Software Suppl
24
26
- Docker Build tool
25
27
- Renovate
26
28
- Integration with DB(s):
27
-
- ClickHouse
28
-
- Cassandra
29
+
- ClickHouse
30
+
- Cassandra
29
31
- Reports: (dependency packages and SBOM/gitbom reports)
30
32
- SBOM
31
33
- Report using Profiling tools Data
@@ -81,15 +83,17 @@ Before starting, make sure you have the following installed and configured:
81
83
2. Trivy - Trivy will be automatically installed if not present
82
84
3. Pyroscope - Pyroscope is up and running, and profiling data is being collected from the application you want to scan. You also need the Pyroscope server URL and the application name
83
85
4. ClickHouse (optional) - If you want to save the data collected by SCSCTL for historical analysis purpose, then make sure ClickHouse is up and running and you have the ClickHouse server URL and the database details
84
-
> If you don't want to save the data, then you can skip this step.
85
-
86
-
> If you want to save the data, then please set the following environment variables:
87
-
The database name will be `scsctl`
88
-
> - `CLICKHOUSE_HOST` - The URL of the ClickHouse server
89
-
> - `CLICKHOUSE_USER` - The username of the ClickHouse server
90
-
> - `CLICKHOUSE_PASSWORD` - The password of the ClickHouse server
91
-
> - `CLICKHOUSE_PORT` - The port of the ClickHouse server
92
-
86
+
87
+
> If you don't want to save the data, then you can skip this step.
88
+
89
+
> If you want to save the data, then please set the following environment variables:
90
+
> The database name will be `scsctl`
91
+
>
92
+
> -`CLICKHOUSE_HOST` - The URL of the ClickHouse server
93
+
> -`CLICKHOUSE_USER` - The username of the ClickHouse server
94
+
> -`CLICKHOUSE_PASSWORD` - The password of the ClickHouse server
95
+
> -`CLICKHOUSE_PORT` - The port of the ClickHouse server
96
+
93
97
### Running the tool
94
98
95
99
1. Clone the repo
@@ -100,19 +104,47 @@ Before starting, make sure you have the following installed and configured:
100
104
6. You can also run the tool using `python app.py` without building the wheel file
101
105
7. After scanning, you can see the reports or rebuild the docker image from the menu
102
106
103
-
104
107
### Commands
105
108
106
109
scsctl has the following commands:
110
+
111
+
- pyroscope_app_name (string) - Pyroscope app name
112
+
- docker_image_name (string) - Docker image name
113
+
- pyroscope_url (string) - Url for pyroscope
114
+
- falco_pod_name (string) - Pod name of falco
115
+
- falco_target_deployment_name (string) - Deployment name of falco
116
+
- db_enabled (boolean) - To enable db saving
117
+
- falco_enabled (boolean) (optional) - To get logs from falco
118
+
- docker_file_folder_path (string) (optional) - Dockerfile folder path if you need to rebuild the image
119
+
- config_file (optional) (YAML)
120
+
107
121
> This command will scan the docker image and generate the reports
0 commit comments