{"id":993,"date":"2016-02-24T18:29:01","date_gmt":"2016-02-25T02:29:01","guid":{"rendered":"http:\/\/raffy.ch\/blog\/?p=993"},"modified":"2017-02-26T15:19:21","modified_gmt":"2017-02-26T23:19:21","slug":"what-would-the-most-mature-security-monitoring-setup-look-like","status":"publish","type":"post","link":"https:\/\/raffy.ch\/blog\/2016\/02\/24\/what-would-the-most-mature-security-monitoring-setup-look-like\/","title":{"rendered":"What Would The Most Mature Security Monitoring Setup Look Like"},"content":{"rendered":"<p>Okay, this post is going to be a bit strange. It&#8217;s a quick brain dump from a technical perspective, what it would take to build the <strong>perfect security monitoring environment<\/strong>.<\/p>\n<p>We&#8217;d need data and contextual information to start with:<\/p>\n<p>Any <strong>data<\/strong>:<\/p>\n<ul>\n<li>infrastructure \/ network logs (flows, dns, dhcp, proxy, routing, IPS, DLP, &#8230;)<\/li>\n<li>host logs (file access, process launch, socket activity, etc.)<\/li>\n<li>HIPS, anti virus, file integrity<\/li>\n<li>application logs (Web, SAP, HR, &#8230;)<\/li>\n<li>metrics<\/li>\n<li>configuration changes (host, network equipment, physical access, applications)<\/li>\n<li>indicators of compromise (threat feeds)<\/li>\n<li>physical access logs<\/li>\n<li>cloud instrumentation data<\/li>\n<li>change tickets<\/li>\n<li>incident information<\/li>\n<\/ul>\n<p>Any <strong>context<\/strong>:<\/p>\n<ul>\n<li>asset information and classification<\/li>\n<li>identity context (roles, etc.)<\/li>\n<li>information classification and location (tracking movement?)<\/li>\n<li>HR \/ presonell information<\/li>\n<li>vulnerability scans<\/li>\n<li>configuration information for each machine, network device, and application<\/li>\n<\/ul>\n<p>With all this information, what are the <strong>different jobs \/ tasks \/ themes<\/strong> that need to be covered from a data consumption perspective?<\/p>\n<ul>\n<li>situational awareness \/ dashboards<\/li>\n<li>alert triage<\/li>\n<li>forensic investigations<\/li>\n<li>metric generation from raw logs \/ mapping to some kind of risk<\/li>\n<li>incident management \/ sharing information \/ collaboration<\/li>\n<li>hunting<\/li>\n<li>running models on the data (data science)<\/li>\n<li>\n<ul>\n<li>anomaly detection<\/li>\n<li>behavioral analysis<\/li>\n<li>scoring<\/li>\n<\/ul>\n<\/li>\n<li>reports (PDF, HTML)<\/li>\n<li>real-time matching against high volume threat feeds<\/li>\n<li>remediating security problems<\/li>\n<li>continuous compliance<\/li>\n<li>controls verification \/ audit<\/li>\n<\/ul>\n<p>What would the right <strong><a href=\"\">data store<\/a><\/strong> look like? What would its capabilities be?<\/p>\n<ul>\n<li>storing any kind of data<\/li>\n<li>kind of schema less but with schema on demand<\/li>\n<li>storing event data (time-stamped data, logs)<\/li>\n<li>storing metrics<\/li>\n<li>fast random access of small amounts of data, aka search<\/li>\n<li>analytical questions<\/li>\n<li>looking for &#8216;patterns&#8217; in the data &#8211; maybe something like a computer science grammar that defines patterns<\/li>\n<li>building dynamic context from the data (e.g., who was on what machine at what time)<\/li>\n<li>anonymization<\/li>\n<\/ul>\n<p>Looks like there would probably be different data stores: We&#8217;d need an index, probably a graph store for complex queries, a columnar store for the analytical questions, pre-aggregated data to answer some of the common queries, and the raw logs as well. Oh boy \ud83d\ude09<\/p>\n<p>I am sure I am missing a bunch of things here. Care to comment?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Okay, this post is going to be a bit strange. It&#8217;s a quick brain dump from a technical perspective, what it would take to build the perfect security monitoring environment. We&#8217;d need data and contextual information to start with: Any data: infrastructure \/ network logs (flows, dns, dhcp, proxy, routing, IPS, DLP, &#8230;) host logs [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,8,35],"tags":[],"class_list":["post-993","post","type-post","status-publish","format-standard","hentry","category-log-analysis","category-security-information-management","category-security-intelligence"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/posts\/993","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/comments?post=993"}],"version-history":[{"count":8,"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/posts\/993\/revisions"}],"predecessor-version":[{"id":1008,"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/posts\/993\/revisions\/1008"}],"wp:attachment":[{"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/media?parent=993"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/categories?post=993"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/raffy.ch\/blog\/wp-json\/wp\/v2\/tags?post=993"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}