Skip to content

Commit ac19dee

Browse files
authored
Merge pull request #832 from crowdsecurity/document_config_paths
add configuration paths
2 parents abcbd68 + a534d8a commit ac19dee

File tree

1 file changed

+73
-0
lines changed

1 file changed

+73
-0
lines changed

crowdsec-docs/docs/configuration/crowdsec_configuration.md

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,79 @@ You can find the default configurations on our GitHub repository:
1515

1616
[Windows default configuration](https://github.com/crowdsecurity/crowdsec/blob/master/config/config_win.yaml)
1717

18+
## Common configuration directories & paths
19+
20+
### `/etc/crowdsec/`
21+
22+
All CrowdSec configuration are living in this directory.
23+
24+
### `/etc/crowdsec/config.yaml`
25+
26+
Main configuration file for Log Processor and Local API.
27+
28+
### `/etc/crowdsec/acquis.d` and `/etc/crowdsec/acquis.yaml`
29+
30+
Documents which log sources and datasources are processed by the Log Processor.
31+
32+
`/etc/crowdsec/acquis.yaml` is the historical acquisition configuration file.
33+
`/etc/crowdsec/acquis.d/*.yaml` is prefered when possible.
34+
35+
### `/etc/crowdsec/bouncers/*.yaml`
36+
37+
Individual configuration file for bouncers.
38+
39+
### `/etc/crowdsec/collections/*.yaml`
40+
41+
Collections currently installed on the Log Processor.
42+
43+
### `/etc/crowdsec/console.yaml`
44+
45+
Console specific flags:
46+
- enable/disable decisions management from the console
47+
- enable/disable sharing of manual decisions with the console
48+
- enable/disable sharing of custom/tainted scenarios related decisions with the console
49+
- enable/disable sharing of alert context data with the console.
50+
51+
### `/etc/crowdsec/contexts/*.yaml`
52+
53+
Enabled alert context for Local API and Log Processor. This is where you should add custom data to be sent in alert context.
54+
55+
### `/etc/crowdsec/hub/`
56+
57+
Local Hub Mirror. Not intended to be modified by the user. Do not put custom scenarios/parsers here.
58+
59+
### `/etc/crowdsec/local_api_credentials.yaml` and `/etc/crowdsec/online_api_credentials.yaml`
60+
61+
Credentials for Local API and Central API.
62+
63+
### `/etc/crowdsec/parsers`
64+
65+
Contains all parsers enabled on the Log Processor, including local parsers, organised in stages:
66+
- `/etc/crowdsec/parsers/s00-raw/*.yaml` : parsers for based formats such as syslog.
67+
- `/etc/crowdsec/parsers/s01-parse/*.yaml` : service specific parsers such as nginx or ssh.
68+
- `/etc/crowdsec/parsers/s02-enrich/*.yaml` : enrichment parsers and whitelists.
69+
70+
71+
### `/etc/crowdsec/scenarios`
72+
73+
Contains all scenarios enabled on the Log Processor, including local scenarios.
74+
75+
### `/etc/crowdsec/profiles.yaml`
76+
77+
Contains profiles used by Local API to eventually turn alerts into decisions or dispatch them to notification plugins.
78+
79+
### `/etc/crowdsec/notifications/*.yaml`
80+
81+
Contains notification plugins configuration (slack, email, splunk, etc.)
82+
83+
### `/etc/crowdsec/appsec-configs/*.yaml`
84+
85+
Contains AppSec (WAF) configuration indicating which rules or loaded in `inband` and `outofband` files, as well as eventual `hooks` configuration.
86+
87+
### `/etc/crowdsec/appsec-rules/*.yaml`
88+
89+
Contains individual AppSec (WAF) rules loaded by `appsec-configs` files.
90+
1891
## Environment variables
1992

2093
It is possible to set configuration values based on environment variables.

0 commit comments

Comments
 (0)