* make it possible to enable json log
* fix
* fix typo
* fix typo
* fix typo
* fix typo
* fix typo
* fix typo
* Add error handling
* Add log_format to default config
* Fix syntax error in if statement
* Fix typo
* Fix typo
* Fix some typos and change naming from native to text, makes more sense
* Set same timestamp format for json logging
* Fix formatting
* Move in if statement under previous
* Fix some formatting that got messed up
* Default to text formatter, if log_format is not configured.
* defining logFormatter outside if statement so that log.SetFormatter(logFormatter) is not undefined when function is called
* Add variables that were undefined
* Argument were missing when calling SetDefaultLoggerConfig function
* Fix order of arguments passed
* Fix order of arguments passed
* Fix typo
* Implicit log_format = "text"
* functional test
* ignore log_format in FatalHook
* make it possible to enable json log
* fix
* fix typo
* fix typo
* fix typo
* fix typo
* fix typo
* fix typo
* Add error handling
* Add log_format to default config
* Fix syntax error in if statement
* Fix typo
* Fix typo
* Fix some typos and change naming from native to text, makes more sense
* Set same timestamp format for json logging
* Fix formatting
* Move in if statement under previous
* Fix some formatting that got messed up
* Default to text formatter, if log_format is not configured.
* defining logFormatter outside if statement so that log.SetFormatter(logFormatter) is not undefined when function is called
* Add variables that were undefined
* Argument were missing when calling SetDefaultLoggerConfig function
* Fix order of arguments passed
* Fix order of arguments passed
* Fix typo
* Implicit log_format = "text"
* functional test
* ignore log_format in FatalHook
* lint
* fix func test
* lint
* remove < > characters from log
---------
Co-authored-by: Victor Edvardsson <victor.edvardsson@loopia.se>
Co-authored-by: marco <marco@crowdsec.net>
Co-authored-by: Thibault "bui" Koechlin <thibault@crowdsec.net>
Add a new datasource that:
- Receives HTTP requests from remediation components
- Apply rules on them to determine whether they are malicious or not
- Rules can be evaluated in-band (the remediation component will block the request directly) or out-band (the RC will let the request through, but crowdsec can still process the rule matches with scenarios)
The PR also adds support for 2 new hub items:
- appsec-configs: Configure the Application Security Engine (which rules to load, in which phase)
- appsec-rules: a rule that is added in the Application Security Engine (can use either our own format, or seclang)
---------
Co-authored-by: alteredCoder <kevin@crowdsec.net>
Co-authored-by: Sebastien Blot <sebastien@crowdsec.net>
Co-authored-by: mmetc <92726601+mmetc@users.noreply.github.com>
Co-authored-by: Marco Mariani <marco@crowdsec.net>
