Safer Pass the salt 2020 Together. Open Source Collaborative - - PowerPoint PPT Presentation

safer
SMART_READER_LITE
LIVE PREVIEW

Safer Pass the salt 2020 Together. Open Source Collaborative - - PowerPoint PPT Presentation

Safer Pass the salt 2020 Together. Open Source Collaborative Dynamic Security engine Crowd Sec VC deck v3.1 Rev : 28/11/2019 Why Cyber defense collaboration is the space race of our generation. Williams David Not solved, for a


slide-1
SLIDE 1

Rev : 28/11/2019

Safer Together.

VC deck v3.1

Open Source Collaborative Security engine Dynamic

CrowdSec

Pass the salt 2020

slide-2
SLIDE 2

Why

“Cyber defense collaboration is the space race of

  • ur generation.”

Williams David

slide-3
SLIDE 3

Not solved, for a reason

Time APPS Money

3

Cloud & Shadow IT

slide-4
SLIDE 4

The next generation solution

4 Real Time Reputation assessment Behavior assessment

Decoupled detection & remediation

Crowd intel sharing

slide-5
SLIDE 5

We use this, because it’s free, real time, fed by community and gives traffic insights. Our parents used this.

Crowd is the remedy to large scale hacking

5 Our goal is to become, “the Waze of Firewalls”

slide-6
SLIDE 6

Building the detection Network with Open Source

slide-7
SLIDE 7

Crowdsec analyses behavior, not IP:port

7

Legitimate traffic Bruteforce Port scan Web crawlers Exploits XSS/SQLi ...

Internet

10.0.0.0/24 12.33.42.155 80/TCP 53/UDP 22/TCP 123.42.56.218 21/TCP

Firewall Crowdsec

slide-8
SLIDE 8

8

Crowdsec is as simple as 1,2,3,4

Logs

BAD IP Community

SIEM Party

Collect data where you want...

Ours Yours Community

Behavior scenarii detect hack attempts React the way you want, where you want

Block Captcha

Limit rights

  • r speed

2FA/MFA

Share your sightings and get informed

BAD IP

1 2 3 4

slide-9
SLIDE 9

9

DEMO TIME

slide-10
SLIDE 10

10

Detecting & enforce

Runs wherever you need it: Logs Logs Logs

Internet

Cloudified, SaaS & Hosted

On Premise Information System

BAD IP BAD IP

slide-11
SLIDE 11

Blockers : Protection at any level

11

  • Relies on local DB fed by API
  • Reusable libraries for integration in most components.
  • Counter-measure is defined by plugin : ban, slow, captcha ...

Simple design allows integration at any level of the stack.

slide-12
SLIDE 12

12

Open Source licensing

Open Source Free (to use, copy, modify)

Free of charge Can be embedded

No usage limit Must name author

Core

MIT License. Core contributors abandon rights Configurations stays their authors properties Blockers stay their authors properties

slide-13
SLIDE 13

Crowdsec

Non elitist security

slide-14
SLIDE 14

14

Easy setup

14

IT engineers on an infrastructure Sysadmins

  • n servers

DevOPS in their deployment environment Developers through a Library or direct API call

Operational install in less than 5 minutes Heavily assisted setup, no technical entry barrier

slide-15
SLIDE 15

CrowdSec

15

Logs & signals from daemons, softwares, frameworks, languages, Cloudtrail, SIEMS, IDS, Firewall...

Acquire Aggregate Normalize Enrich CrowdSec 3rd party Local data Heuristics Rulesets Analysis Upload signal Apply action Store event Coded in GO, runs on all major OS Engineered for Cloud, Kubs, VMs

Timestamp Offending IP Target type Attack type Up to date bad IP list

Inference Engine

slide-16
SLIDE 16

Configuration Hub

16

One place to find community scenarios. One click to enable them.

slide-17
SLIDE 17

Visualisation

17

One command to access reporting. Relying on metabase.

slide-18
SLIDE 18

Technical takeaways : Crowdsec

18

Written in golang, community driven Observability, for users and OPs Lightweight and declarative for versatile deployment

slide-19
SLIDE 19

Crowd fed decisions

Stronger together

slide-20
SLIDE 20

20

One stone, ten birds

?

Aggressive traffic is qualified, discarded & notified to our database

slide-21
SLIDE 21

The secret sauce: Consensus

21

Predictive.Alg

Honeypot

Crowd Sec Crowd Sec

TR1 TR1 TR1 TR1

TR2 TR2 TR2

Canaries

Crowd Sec

slide-22
SLIDE 22

We broadcast “canaries”, IP whitelists of trustable actors (ie so that you won’t ruin your SEO by banning Google by mistake)

22

You will generate False Positives

If a scenario (community or Crowdsec one) kicks a whitelisted IP, it is marked as potentially triggering FP. Those IP addresses are crowdsourced as well, on our Github project, and curated by our staff, to diversify sources If a previously trusted actor changes behavior, we’ll notice it by having reliable scenarii being triggered by those, now evil, canaries

slide-23
SLIDE 23

Thank you

Only the crowd can defeat mass scale hacking... Crowdsec.net github.com/crowdsecurity/crowdsec