Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Uso y depliegue de osquery para detección de a...

Uso y depliegue de osquery para detección de amenazas a escala

Éste taller se centra en el uso práctico de osquery en la detección de actividades maliciosas y su despliegue a escala para una respuesta a incidentes efectiva. Desde su uso en un sistema aislado con logs almacenados localmente, hasta formar parte de una red compleja con miles de hosts, y con gestión bi-direccional centralizada.

Javier Marcos

June 21, 2019
Tweet

More Decks by Javier Marcos

Other Decks in Technology

Transcript

  1. Taller de uso y despliegue de osquery Para detección de

    amenazas a escala Javier Marcos @javutin EUSKALHACK 2019
  2. ▪ Security Engineer/Incident Responder ▪ Open source contributor (github.com/javuto) ▪

    Former IBM, Facebook, Uber and Airbnb ▪ Current -> $ whoami
  3. Part 1: osquery, let’s talk about it ▪ What is

    it? ▪ osqueryi basics ▪ osquery tables ▪ Package files (break) Agenda
  4. Agenda Part 2: Scaling osquery ▪ Do you need a

    Daemon? osqueryd! ▪ Flags and configuration files ▪ Scheduled queries, packs and watchdog ▪ Remote API: TLS endpoint (osctrl) (end)
  5. osquery packages MacOS: brew install osquery Windows: choco install osquery

    APT Linux: sudo apt-get install osquery RPM Linux: sudo yum install osquery FreeBSD: pkg install osquery https://osquery.io/downloads
  6. What is osquery? ▪ Explore your operative system using SQL

    ▪ Host visibility motivated by intrusion detection 100% OS API usage, no fork execve • https://osquery.io • https://github.com/facebook/osquery
  7. osquery motivation ▪ What machines have chrome extension abc123 installed?

    ▪ How many file descriptors were open yesterday by hour? ▪ Is anything bridging routes from VPN to LAN?
  8. Why use SQL? ▪ Core concepts of SQL are platform

    agnostic ▪ Most devs and administrators know SQL SELECT pid,name,uid FROM processes
  9. Why use SQL? WHERE uid != 0 [constraints] [join] JOIN

    users ON processes.uid=users.uid SELECT pid,name,uid FROM processes [attributes] [concept]
  10. osqueryi basics osquery> .help Welcome to the osquery shell. Please

    explore your OS! You are connected to a transient 'in-memory' virtual database. .all [TABLE] Select all from a table .bail ON|OFF Stop after hitting an error .echo ON|OFF Turn command echo on or off .exit Exit this program .features List osquery's features and their statuses .headers ON|OFF Turn display of headers on or off .help Show this message
  11. osqueryi basics => crontab => curl => curl_certificate => deb_packages

    => device_file => device_hash => device_partitions => disk_encryption => dns_resolvers => docker_container_labels => docker_container_mounts => docker_container_networks => docker_container_ports osquery> .tables => acpi_tables => apt_sources => arp_cache => augeas => authorized_keys => block_devices => carbon_black_info => carves => chrome_extensions => cpu_time => cpuid
  12. osqueryi basics osquery> pragma table_info(‘system_info’); +-----+--------------------+---------+---------+------------+----+ | cid | name

    | type | notnull | dflt_value | pk | +-----+--------------------+---------+---------+------------+----+ | 0 | hostname | TEXT | 0 | | 0 | | 1 | uuid | TEXT | 0 | | 0 | | 2 | cpu_type | TEXT | 0 | | 0 | | 3 | cpu_subtype | TEXT | 0 | | 0 | | 4 | cpu_brand | TEXT | 0 | | 0 | | 5 | cpu_physical_cores | INTEGER | 0 | | 0 | | 6 | cpu_logical_cores | INTEGER | 0 | | 0 | | 7 | cpu_microcode | TEXT | 0 | | 0 |
  13. osquery tables ▪ 229 tables in version 3.3.2 ▪ 4

    different platforms ▫ Mac, windows, linux and freebsd ▪ Data easy to collect and to join https://osquery.io/schema/3.3.2
  14. osquery tables https://osquery.io/schema/3.3.2 ▪ acpi_tables ▪ arp_cache ▪ apps ▪

    authorized_keys ▪ autoexec ▪ battery ▪ block_devices ▪ browser_plugins ▪ certificates ▪ cpu_time ... ▪ cpu_info ▪ crontab ▪ cups_jobs ▪ deb_packages ▪ disk_info ▪ dns_resolvers ▪ docker_info ▪ drivers ▪ etc_hosts ▪ elf_info ... ▪ etc_services ▪ event_taps ▪ file ▪ iptables ▪ kernel_info ▪ known_hosts ▪ launchd ▪ mounts ▪ preferences ... And many more!
  15. Tables execute when used osquery> SELECT datetime FROM time; +----------------------+

    | datetime | +----------------------+ | 2019-03-01T04:16:07Z | +----------------------+ ...
  16. Tables execute when used osquery> SELECT datetime FROM time; +----------------------+

    | datetime | +----------------------+ | 2019-03-01T04:20:18Z | +----------------------+ ...
  17. Tables with parameters osquery> SELECT directory FROM file WHERE path

    = ‘/etc/issue’; +-----------+ | directory | +-----------+ | /etc | +-----------+
  18. Tables with parameters osquery> SELECT md5 FROM file JOIN hash

    USING (path) WHERE path = ‘/etc/issue’; +----------------------------------+ | md5 | +----------------------------------+ | b954418e6a50d4d4cb8f02776d867550 | +----------------------------------+
  19. Tables easy to collect osquery> SELECT * FROM deb_packages; osquery>

    SELECT * FROM users; osquery> SELECT * FROM kernel_modules; osquery> SELECT * FROM startup_items;
  20. osquery files in Linux ▪ deb/rpm /etc/osquery/osquery.conf ← Config /var/log/osquery

    ← Logs /usr/bin ← Bins /usr/share/osquery/packs ← Packs
  21. osquery files in Mac OS ▪ brew/pkg /var/osquery/osquery.conf ← Config

    /var/log/osquery ← Logs /usr/local/bin ← Bins /var/osquery/packs ← Packs
  22. osquery files in Windows ▪ choco/msi C:\Program Files\osquery\osquery.conf ← Config

    C:\Program Files\osquery\log ← Logs C:\Program Files\osquery\ ← Bins C:\Program Files\osquery\packs ← Packs
  23. Quiz! ▪ What is the system hostname? ▪ What users

    exist on the system? ▪ What processes are running?
  24. Quiz! ▪ What is the system hostname? ▪ What users

    exist on the system? ▪ What processes are running? SELECT hostname FROM system_info;
  25. Quiz! ▪ What is the system hostname? ▪ What users

    exist on the system? ▪ What processes are running? SELECT hostname FROM system_info; SELECT uid, username FROM users;
  26. Quiz! ▪ What is the system hostname? ▪ What users

    exist on the system? ▪ What processes are running? SELECT hostname FROM system_info; SELECT uid, username FROM users; SELECT pid, name, path FROM processes;
  27. Quiz! ▪ What is the username and the shell of

    the user that has a running process?
  28. Quiz! ▪ What is the username and the shell of

    the user that has a running process? SELECT p.pid, p.name, p.path, u.username, u.shell FROM processes AS p JOIN users AS u ON p.uid = u.uid;
  29. The osquery daemon: osqueryd ▪ Init, systemd, launchd, win service

    ▪ Queries executed on schedule ▪ Logs for daemon status and query results ▪ Heavily configurable
  30. The osquery daemon: osqueryd intrusion detection use cases centralized management

    (backend) operative system, users, services configuration logging osqueryd
  31. osquery.flags ▪ Flagfile can bootstrap how to config $ osqueryd

    --flagfile /etc/osquery/osquery.flags ▪ It is common to use chef/puppet to write flags $ osqueryd/osqueryi --help
  32. osquery.conf - options $ osquery[d-i] --config_path /path/to/osquery.conf "options": { "config_plugin":

    "filesystem", "logger_plugin": "filesystem", "schedule_splay_percent": "10", "utc": "true" ... }
  33. osquery.conf - schedule "schedule": { "example_query1": { "query": "SELECT *

    FROM users;", "interval": 60 }, "example_query2": { "query": "SELECT * FROM processes;", "interval": 3600 }, }
  34. Scheduled queries query: The exact query string to run interval:

    Run the query every this seconds platform: Restrict query to this platform shard: Only run on this % of hosts snapshot: Return all results on each execution
  35. osquery.conf - decorators "decorators": { "load": [ "SELECT uuid FROM

    system_info;" ], "always": [ "SELECT pid FROM osquery_info;" ] }
  36. osquery.conf - packs "packs": { "osquery-monitoring": "osquery-monitoring.conf", "incident-response": "incident-response.conf", "it-compliance":

    "it-compliance.conf", "osx-attacks": "osx-attacks.conf", "vuln-management": "vuln-management.conf" "hardware-monitoring": "hardware-monitoring.conf", "ossec-rootkit": "ossec-rootkit.conf", "windows-hardening": "windows-hardening.conf", "windows-attacks": "windows-attacks.conf" },
  37. osquery.conf - packs // incident-response.conf "queries": { "launchd": { "query"

    : "select * from launchd;", "interval" : "3600", "platform" : "darwin", "version" : "1.4.5", }, ...
  38. osqueryd watchdog ▪ osqueryd by default works on a single

    worker ▪ Periodically inspects CPU/memory usage ▪ restart if: Over 60% CPU usage for 9 s ▪ restart if: Over 200M memory allocated
  39. osqueryd remote API ▪ TLS endpoint allows Distributed queries ➔

    On demand queries ➔ Return results immediately on a pull model ➔ Very useful for investigations
  40. osqueryd remote API ▪ Options for TLS endpoint solutions ➔

    SGT ➔ Windmill ➔ CB LiveOps ➔ AlienVault ➔ Doorman ➔ Uptycs ➔ Kolide ➔ Zentral
  41. osqueryd remote API ▪ Enroll POST /path/to/enroll ▪ Configuration POST

    /path/to/config https://osquery.readthedocs.io/en/stable/deployment/remote/ ▪ Logs POST /path/to/log ▪ Extras (On-demand queries) (File carving) ...
  42. osqueryd remote API ▪ TLS Plugin allows for remote configuration

    + flags --tls_client_cert Optional path to a TLS client-auth PEM certificate --tls_client_key Optional path to a TLS client-auth PEM private key --tls_hostname TLS/HTTPS hostname for Config, Logger, and Enroll --tls_server_certs Optional path to a TLS server PEM certificate(s) bundle https://osquery.readthedocs.io/en/stable/deployment/remote/
  43. Bonus: advanced osquery ▪ FIM (File Integrity Monitoring) ▪ Tablas

    de eventos / audit ▪ Extensiones de osquery (C/C++, Go, Python) ▪ Tablas custom con ATC (Automated Table Construction)
  44. File Integrity Monitoring (FIM) "file_paths": { "homes": ["/home/*"] }, "schedule":

    { "file_events": { "query": "SELECT * FROM file_events;", "interval": 300 } }
  45. File Integrity Monitoring (FIM) ▪ Events tables: file_events ▪ Subscribe

    to async OS events ▪ osquery will buffer these events over time ▪ Selecting from the table shows a slice https://osquery.readthedocs.io/en/stable/deployment/file-integrity-monitoring/
  46. Yara rules hunting "yara": { "signatures": { "sig_group_1": [ "/tmp/foo.sig",

    "/tmp/bar.sig"], "sig_group_2": [ "/tmp/baz.sig" ] }, "file_paths": { } }
  47. Yara rules hunting ▪ Events table: yara_events ▪ Also on-demand

    scanning: SELECT * FROM yara WHERE path="/bin/ls" AND sig_group="sig_group_1"; https://osquery.readthedocs.io/en/stable/deployment/yara/
  48. osquery extensions $ osquery[d-i] --extension /path/to/my_extension.ext ▪ Write them in

    C++, python and golang… ▪ Or any other language that supports Thrift https://osquery.readthedocs.io/en/stable/development/osquery-sdk/