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
@@ -24,17 +32,8 @@ In addition to logs, Pipeleak can also scan artifacts generated by your pipeline
24
32
25
33
Note: Scanning artifacts uses a lot of memory!
26
34
```bash
27
-
pipeleak scan --token glpat-xxxxxxxxxxx --gitlab https://gitlab.com -a
28
-
```
29
-
30
-
**Pro tip:**
31
-
32
-
> Note: [Dotenv artifacts](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportsdotenv) are not accessible through the GitLab API. To scan these, you need to manually provide your session cookie after logging in via a web browser. The session cookie name is `_gitlab_session`. The cookie should be valid for [two weeks](https://gitlab.com/gitlab-org/gitlab/-/issues/395038).
33
-
34
-
```bash
35
-
pipeleak scan --token glpat-xxxxxxxxxxx --gitlab https://gitlab.com -v -a -c [value-of-valid-_gitlab_session]
35
+
pipeleak gl scan --token glpat-xxxxxxxxxxx --gitlab https://gitlab.com -a
36
36
```
37
-
38
37
### Confidence
39
38
40
39
The following confidence levels for scans are used by default:
@@ -46,7 +45,27 @@ The following confidence levels for scans are used by default:
46
45
However if you want to add custom ones, you can define any value in the `rules.yml` file
47
46
To scan only for a specific level, you can specify it via CLI flag e.g `--confidence=high,medium`. Define multiple by comma separating the values.
48
47
49
-
Note: `high-verified` cannot be removed.
48
+
Note: `high-verified` cannot be removed, but verification can be disabled using `--truffleHogVerification=false`.
49
+
50
+
### Customizing Scan Rules
51
+
52
+
When you run Pipeleak for the first time, it generates a `rules.yml` file based on [this repository](https://github.com/mazen160/secrets-patterns-db/blob/master/db/rules-stable.yml). You can customize your scan rules by modifying this file as needed.
53
+
54
+
### Keybindings
55
+
56
+
In the `scan` mode you can change interactively between log levels by pressing `t`: Trace, `d`: Debug, `i`: Info, `w`: Warn, `e`: Error. Pressing `s` will output the current queue status.
57
+
58
+
# Platform Specific Hints
59
+
60
+
## GitLab
61
+
62
+
### Dotenv
63
+
64
+
[Dotenv artifacts](https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html#artifactsreportsdotenv) are not accessible through the GitLab API. To scan these, you need to manually provide your session cookie after logging in via a web browser. The session cookie name is `_gitlab_session`. The cookie should be valid for [two weeks](https://gitlab.com/gitlab-org/gitlab/-/issues/395038).
In the `scan` mode you can change interactively between log levels by pressing `t`: Trace, `d`: Debug, `i`: Info, `w`: Warn, `e`: Error. Pressing `s` will output the current queue status.
98
+
No remarks yet 🌟
80
99
81
-
##ELK Integration
100
+
# ELK Integration
82
101
83
102
To easily analyze the results you can [redirect the pipeleak](https://github.com/deviantony/docker-elk?tab=readme-ov-file#injecting-data) output using `nc` into Logstash.
84
103
85
104
Setup a local ELK stack using https://github.com/deviantony/docker-elk.
Using Kibana you can filter for interesting messages, based on the JSON attributes of the output.
93
112
94
113
e.g. `message.level=warn and message.confidence=verified` to find verified results.
95
114
96
-

97
-
98
-
## Customizing Scan Rules
99
-
100
-
When you run Pipeleak for the first time, it generates a `rules.yml` file based on [this repository](https://github.com/mazen160/secrets-patterns-db/blob/master/db/rules-stable.yml). You can customize your scan rules by modifying this file as needed.
0 commit comments