<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[OSCD - Medium]]></title>
        <description><![CDATA[Open international cybersecurity specialist initiative. We collaborate on common problems and share knowledge. - Medium]]></description>
        <link>https://medium.com/oscd?source=rss----bfea556c7193---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>OSCD - Medium</title>
            <link>https://medium.com/oscd?source=rss----bfea556c7193---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:32:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/oscd" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[OSCD Sprint # 2: Detection, Simulation & Response, итоги (RU)]]></title>
            <link>https://medium.com/oscd/oscd-sprint-2-detection-simulation-response-%D0%B8%D1%82%D0%BE%D0%B3%D0%B8-ru-4143577becf?source=rss----bfea556c7193---4</link>
            <guid isPermaLink="false">https://medium.com/p/4143577becf</guid>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[the-hive]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <dc:creator><![CDATA[Open Security Collaborative Development]]></dc:creator>
            <pubDate>Tue, 19 Apr 2022 00:51:25 GMT</pubDate>
            <atom:updated>2022-04-23T16:28:11.217Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*tkPfZJq67NUdCtkkgc5BCg.gif" /></figure><blockquote><em>Оригинальная дата публикации — 10.09.2021</em></blockquote><p>Open Security Collaborative Development — это открытая международная инициатива специалистов по компьютерной безопасности. Мы совместно решаем общие проблемы и распространяем знания.</p><p>Первый спринт под названием “Threat Detection” прошел в октябре 2019 года, и был посвящен разработке правил обнаружения угроз проекта <a href="https://github.com/SigmaHQ/sigma">Sigma</a> для расширения покрытия фреймворка <a href="https://attack.mitre.org/">MITRE ATT&amp;CK®</a>. Тогда нам удалось увеличить публичный набор правил на 40%, разработав 144 новых правила. Листинг правил доступен в описании<a href="https://github.com/Neo23x0/sigma/pull/554"> Pull Request</a> в репозитории Sigma на GitHub. Итоги были опубликованы на <a href="https://medium.com/oscd/oscd-threat-detection-sprint-1-%D0%B8%D1%82%D0%BE%D0%B3%D0%B8-ru-3b3a9f643278">Medium</a>.</p><p><a href="https://oscd.community/sprints/sprint_2_ru.html">Второй спринт</a> прошел в октябре 2020 года и о нём мы расскажем в этой статье.</p><h3>Подготовка</h3><p>Команда MITRE ATT&amp;CK,​ незадолго до начала спринта, выпустила новую версию фреймворка, введя новую сущность — <a href="https://medium.com/mitre-attack/attack-with-sub-techniques-is-now-just-attack-8fc20997d8de">sub-techniques</a>. Ее добавление повлекло за собой обновление ID большинства техник. Для разработки детального бэклога <a href="https://github.com/SigmaHQ/sigma/pull/989">мы обновили тэги</a> <strong>всех</strong> правил репозитория Sigma в соответствии с нововведениями; проверили 644 правила и обновили 513.</p><p>Мы разработали и опубликовали <a href="https://oscd.community/sprints/sprint_2_backlog_ru.html">бэклог</a>, в котором для каждой задачи привели оценку времени выполнения (Estimated Time to Complete или ETC) и необходимые для их решения знания. В разделе <a href="https://oscd.community/sprints/sprint_2_howto_ru.html">How-To</a> мы также описали способы получения этих знаний. Таким образом, участники могли заранее определить посильный набор задач на этот спринт, сопоставив их описание со своим свободным временем и наличием релевантных компетенций.</p><p>На основании бэклога мы сформировали Issue к репозиториям целевых проектов на GitHub. При этом команды целевых проектов спринта создали отдельные ветки в репозиториях для OSCD, за что им отдельное спасибо. В Issue участники подробно расписали подзадачи и описали теоретическую базу, необходимую для решения, привели ссылки на соответствующие исследования и ресурсы, и ссылки на предыдущие работы сообщества по каждой подзадаче.</p><p>Мы разработали карты MITRE ATT&amp;CK​ Navigator с зонами покрытия техник злоумышленников правилами обнаружения репозитория Sigma и тестами эмуляции угроз из репозитория <a href="https://github.com/redcanaryco/atomic-red-team">Atomic Red Team</a>: одну общую карту <a href="https://mitre-attack.github.io/attack-navigator/enterprise/#layerURL=https%3A%2F%2Fraw%2Egithubusercontent%2Ecom%2Foscd%2Dinitiative%2FSigma%2DART%2DATTCK%2DNavigator%2DLayer%2Fmaster%2FSigmaART%2DATT%2526CKNavigatorLayer%2Ejson">Sigma + ART</a> и отдельные карты в разрезе операционных систем <a href="https://mitre-attack.github.io/attack-navigator/#layerURL=https%3A%2F%2Fraw.githubusercontent.com%2Foscd-initiative%2FOSCD_Sigma-ART_Layers%2Fmaster%2Fsigma-art-navigator-layer-windows.json">Sigma + ART Windows</a> | <a href="https://mitre-attack.github.io/attack-navigator/enterprise/#layerURL=https%3A%2F%2Fraw.githubusercontent.com%2Foscd-initiative%2FOSCD_Sigma-ART_Layers%2Fmaster%2Fsigma-art-navigator-layer-linux.json">Sigma + ART GNU\Linux</a> | <a href="https://mitre-attack.github.io/attack-navigator/enterprise/#layerURL=https%3A%2F%2Fraw.githubusercontent.com%2Foscd-initiative%2FOSCD_Sigma-ART_Layers%2Fmaster%2Fart-navigator-layer-macos.json">ART macOS</a>.</p><p>Аналогичным образом <a href="https://oscd-initiative.github.io/react-navigator/">мы визуализировали</a> текущее и возможное покрытие действий реагирования на инциденты фреймворка <a href="https://github.com/atc-project/atc-react">ATC RE&amp;CT</a> модулями автоматизированного анализа (Analyzers) и реагирования (Responders) платформы <a href="http://thehive-project.org/">TheHive</a>.</p><p>Визуализации покрытия фреймворков ATT&amp;CK и RE&amp;CT в последствии помогут нам оценить реальный эффект наших совместных действий.</p><h3>Начало</h3><p>5 Октября 2020 года начался <a href="https://twitter.com/oscd_initiative/status/1305748180517224449?s=20">второй спринт</a> под названием “Simulation, Detection &amp; Response”. В скоуп добавились еще два целевых проекта:</p><ul><li>Atomic Red Team — набор портативных тестов для проверки возможностей по обнаружению угроз, с привязкой к MITRE ATT&amp;CK​. Команды защиты проверяют правила детектирования, посредством запуска “атомарных тестов”, которые воспроизводят техники злоумышленников. Проект Atomic Red Team стал самым большим и зрелым набором тестов для эмуляции угроз, управляемым сообществом;</li><li>TheHive — платформа для реагирования на инциденты с открытым исходным кодом, включающая в себя модуль под названием <a href="https://thehive-project.org/#section_cortex">Cortex</a> — движок для анализа данных и активного реагирования на инциденты, который использует Analyzers (Анализаторы) и Responders (модули Реагирования). Это Python-скрипты, использующие различные транспорты (включая API) для коммуникации со сторонними системами и выполнения определенных действий по реагированию.</li></ul><h3>Как это было</h3><p>Общение участников во время спринта происходило в Issues и Pull Requests к репозиториям целевых проектов на GitHub. Мы отказались от чатов, потому что в прошлый раз от них не было пользы. Не смотря на это, было много ярких примеров открытого и продуктивного общения. Например, в процессе разработки аналитики для <a href="https://github.com/SigmaHQ/sigma/pull/1033/files/c878d55ac0fd97d7f7fedebc3e15e4ad85326405#r501979040">обнаружения техник Lateral Movement</a>, участники тэгнули в обсуждении на <a href="https://twitter.com/HeirhabarovT">Теймура Херхабарова</a> — автора нескольких исследований по этой теме. Он оперативно вышел на связь и помог найти ответ.</p><p>Замечания или корректировки к решениям других участников оформлялись в виде предложений, с просьбой рассмотреть или попробовать иной подход. При этом предложения сопровождались обоснованием с конкретными примерами и ссылками.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5yZ5E4YGBIPs5icmTzZ7_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*COPOykxspYZ2NvD0IIhliQ.png" /><figcaption>Примеры обсуждений</figcaption></figure><h3>География: 🇺🇸 🇷🇺 🇵🇱 🇹🇷 🇦🇺 🇨🇦 🇫🇷 🇮🇳 🇦🇪 🇦🇹 🇧🇷 🇩🇪 🇪🇸 🇳🇱 🇮🇱 🇭🇺 🇸🇬</h3><p>OSCD создавалась как международная инициатива, и мы очень рады наблюдать как она растет: в этот раз в спринте участвовало это <strong>в</strong> <strong>три раза </strong>больше<strong> </strong>специалистов — 47 человек из 17 стран.</p><h3>Результаты</h3><p>Результаты были оформлены в виде Pull Requests в GitHub репозиториях целевых проектов. Вот что нам удалось сделать:</p><ul><li>разработали 287 правила Sigma. Участники инициативы добавили 242 правила и обновили 305 старых <a href="https://github.com/SigmaHQ/sigma/pull/1362">(Pull Request)</a>. 45 новых правил разработали коллеги из <a href="https://twitter.com/otr_community">OTR Community</a> <a href="https://github.com/SigmaHQ/sigma/pull/1158">(Pull Request)</a>;</li></ul><blockquote>Мы второй раз увеличили набор правил Sigma более чем на 30%!</blockquote><ul><li>разработали 23 теста эмуляции Atomic Red Team и обновили 7 старых (<a href="https://github.com/redcanaryco/atomic-red-team/pull/1431">Pull Request</a>);</li><li>разработали 24 TheHive Responder’а для автоматизации действий реагирования в системах Palo Alto NGFW, Duo Security, Gmail и Azure Active Directory (<a href="https://github.com/TheHive-Project/Cortex-Analyzers/pull/991">Pull Request</a>);</li><li>разработали 1 TheHive Analyzer для автоматизации анализа IOC и CVE в Vulners.com (<a href="https://github.com/TheHive-Project/Cortex-Analyzers/pull/880">Pull Request</a>).</li></ul><p>Это пример результатов, которых можно достичь посредством глобального сотрудничества над решением общих проблем в области информационной безопасности. Практическое взаимодействие, которого, на наш взгляд, нам очень недостает.</p><h3>Список участников</h3><p>Список также доступен на <a href="https://oscd.community/index_ru.html">нашем сайте</a>.</p><p>🇺🇸 Грэг Хауэлл | <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 <a href="http://twitter.com/Cyb3rPandaH">Хосэ Родригез</a> | <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 <a href="http://twitter.com/neu5ron">Нэйт Нуагенти</a> | <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 Патрик Джон | <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 <a href="http://twitter.com/Cyb3rWard0g">Роберто Родригез</a> | <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 <a href="http://twitter.com/craigtweets">Крейг Янг</a> | <a href="https://www.tripwire.com/">Tripwire</a><br>🇺🇸 <a href="http://twitter.com/DanielWeiner93">Даниэл Вайнер</a> | Независимый Исследователь<br>🇺🇸 Харе Судхан Муфусами | Независимый Исследователь<br>🇺🇸 <a href="http://twitter.com/remotephone">Джэйми Флорес</a> | Независимый Исследователь<br>🇺🇸 <a href="http://twitter.com/JohnLaTwC">Джон Ламберт</a> | <a href="https://microsoft.com/">Microsoft</a><br>🇺🇸 <a href="http://twitter.com/tuckner">Джон Такнер</a> | Независимый Исследователь<br>🇺🇸 <a href="http://twitter.com/WordPlas">Райан Плас</a> | <a href="https://www.stage2sec.com/">Stage 2 Security</a><br>🇷🇺 Денис Бею | Независимый Исследователь<br>🇷🇺 <a href="http://twitter.com/Dmitry_U4">Дмитрий Учакин</a> | <a href="https://www.kaspersky.com/">Kaspersky Lab</a>/<a href="https://vulners.com/">Vulners.com</a><br>🇷🇺 Игорь Фиц | Независимый Исследователь<br>🇷🇺 <a href="http://twitter.com/CatSchrodinger">Ильяс Очков</a> | Независимый Исследователь<br>🇷🇺 Максим Конакин | Независимый Исследователь<br>🇷🇺 Наталия Шорникова | <a href="https://www.izsoc.ru/">IZ SOC</a><br>🇷🇺 <a href="http://twitter.com/HeirhabarovT">Теймур Хеирхабаров</a> | <a href="https://www.bi.zone/">BI.ZONE SOC</a><br>🇷🇺 <a href="http://twitter.com/vasebur">Василий Буров</a> | Независимый Исследователь<br>🇵🇱 <a href="http://twitter.com/bczyz1">Бартоломей Чиж</a> | Независимый Исследователь<br>🇵🇱 <a href="http://twitter.com/mrblacyk">Якоб Вайнзетл</a> | <a href="https://www.tieto.com/en/what-we-do/managed-services-and-integration/security-services/security-operations-center/">Tieto SOC</a><br>🇵🇱 <a href="http://twitter.com/sn0w0tter">Матэуш Выдра</a> | <a href="https://www.relativity.com/ediscovery-software/relativityone/trust/threat-prevention/our-team/">Relativity</a><br>🇵🇱 <a href="http://twitter.com/aestimi">Тим Исмиляев</a> | <a href="https://www.manasecurity.com/">Mana Security</a><br>🇹🇷 <a href="http://twitter.com/sblmsrsn">Энсар Самиль</a> | Независимый Исследователь<br>🇹🇷 <a href="http://twitter.com/caliskanfurkan_">Фуркан Калискан</a> | <a href="https://www.ziraatteknoloji.com/">Ziraat Teknoloji</a><br>🇹🇷 <a href="http://twitter.com/semanurtg">Семанур Гюнейсу</a> | <a href="https://www.destel.com.tr/">DESTEL/SOC</a><br>🇹🇷 <a href="http://twitter.com/ogunal00">Омар Гунал</a> | Независимый Исследователь<br>🇦🇺 <a href="http://twitter.com/CyberRaiju">Джай Минтон</a> | Независимый Исследователь<br>🇦🇺 Джонатан Чейонг | Независимый Исследователь<br>🇦🇺 <a href="http://twitter.com/svch0st">Зак Стэнфорд</a> | <a href="https://twitter.com/CxCyber">CyberCX</a><br>🇨🇦 <a href="http://twitter.com/v3t0_">Авнет Синх</a> | Независимый Исследователь<br>🇨🇦 <a href="http://twitter.com/tas_kmanager">Мангатас Тонданг</a> | Независимый Исследователь<br>🇫🇷 <a href="http://twitter.com/gregclermont">Грэгори Клермонт</a> | Независимый Исследователь<br>🇫🇷 <a href="http://twitter.com/nadouani">Набил Адуани</a> | <a href="https://thehive-project.org/">TheHive</a>/<a href="https://www.strangebee.com/">StrangeBee</a><br>🇮🇳 <a href="http://twitter.com/iamkirankmr">Киран Кумар</a> | Независимый Исследователь<br>🇮🇳 <a href="http://twitter.com/OG0Sec">Омар Гудхат</a> | Независимый Исследователь<br>🇦🇪 <a href="http://twitter.com/stvetro">Виктор Сергеев</a> | <a href="https://www.helpag.com/">Help AG</a><br>🇦🇹 <a href="http://twitter.com/Strassi7">Дэвид Страбэггер</a> | Независимый Исследователь<br>🇧🇷 <a href="http://twitter.com/_w0rk3r">Джонатан Рибейро</a> | Независимый Исследователь<br>🇩🇪 <a href="http://twitter.com/blubbfiction">Томас Пацке</a> | <a href="https://github.com/SigmaHQ/sigma">Sigma Project</a><br>🇪🇸 <a href="http://twitter.com/aomanzanera">Алехандро Ортуно</a> | Независимый Исследователь<br>🇭🇺 <a href="http://twitter.com/AcsGacs">Гиоргий Акс</a> | <a href="https://cisco.com/">Cisco</a><br>🇮🇱 Ели Салем | Независимый Исследователь<br>🇳🇱 Сэндер Вейбинг | <a href="https://www.nfir.nl/">NFIR B.V.</a><br>🏳️ <a href="http://twitter.com/yugoslavskiy">Даниил Югославский</a> | <a href="https://twitter.com/atc_project">Atomic Threat Coverage</a><br>🇸🇬 Глеб Суходольский | Независимый Исследователь</p><p>Спасибо вам! (:</p><p>Кстати, мы создали <a href="https://www.linkedin.com/company/oscd-initiative/">организацию в LinkedIn</a>, теперь вы можете отметить участие в спринтах в как волонтерский опыт:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MoIIp-K7VcfoccuYzr7FmQ.png" /></figure><h3>Хочу участвовать</h3><p>В OSCD нет входных требований для участников. Работа ведется открыто и исключительно в интересах сообщества, не для обогащения и без связей с коммерческими организациями.<br>Следите за новостями в <a href="https://twitter.com/oscd_initiative">Twitter</a> или в <a href="https://t.me/oscd_initiative">Telegram</a>, дождитесь объявления о начале следующего спринта, выберите себе задачу из бэклога или предложите свою, и разработайте решение вместе с сообществом!</p><h3>Полезные ссылки</h3><ul><li>Наш <a href="https://oscd.community/">вебсайт</a></li><li>Наш <a href="https://twitter.com/oscd_initiative">twitter</a>; зеркало в <a href="https://t.me/oscd_initiative">telegram</a></li><li><a href="https://twitter.com/i/lists/1308954210470428672">List участников OSCD в Twitter</a></li></ul><blockquote><em>Оригинальная дата публикации — 10.09.2021</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4143577becf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oscd/oscd-sprint-2-detection-simulation-response-%D0%B8%D1%82%D0%BE%D0%B3%D0%B8-ru-4143577becf">OSCD Sprint # 2: Detection, Simulation &amp; Response, итоги (RU)</a> was originally published in <a href="https://medium.com/oscd">OSCD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSCD Sprint # 2: Detection, Simulation & Response, results (EN)]]></title>
            <link>https://medium.com/oscd/oscd-sprint-2-detection-simulation-response-results-43fd9298128c?source=rss----bfea556c7193---4</link>
            <guid isPermaLink="false">https://medium.com/p/43fd9298128c</guid>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[the-hive]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <dc:creator><![CDATA[Open Security Collaborative Development]]></dc:creator>
            <pubDate>Mon, 18 Apr 2022 23:31:08 GMT</pubDate>
            <atom:updated>2022-04-23T16:27:50.791Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*tkPfZJq67NUdCtkkgc5BCg.gif" /></figure><blockquote><em>Original publication date — September 10, 2021</em></blockquote><p>Open Security Collaborative Development (OSCD) is an open international cybersecurity specialist initiative. We collaborate on common problems and share knowledge.</p><p>Two-week sprints were chosen as the work format. This time is enough to plunge into the essence of the problems being solved, while the limited time prevents endless rework in pursuing perfection.</p><p>The first OSCD sprint took place in October 2019 and was called “Threat Detection”. That time we focused on threat detection rules development in Sigma format to improve <a href="https://attack.mitre.org/">MITRE ATT&amp;CK®</a> coverage.</p><p>We’ve increased the ruleset of the Sigma Project by more than 40%, contributing 144 new rules. The sprint summary was published on <a href="https://medium.com/oscd/oscd-threat-detection-sprint-1-results-en-a78742d2e67a">Medium</a> and the <a href="https://oscd.community/sprints/sprint_1.html">initiative’s website</a>.</p><p><a href="https://oscd.community/sprints/sprint_2.html">The second sprint</a> took place in October 2020, which we are going to talk about in this article.</p><h3>Preparation</h3><p>Before the start of the sprint, it was necessary to carry out preparatory work. In this section, we will consider in more detail what had to be done to make it convenient and easy for the participants to complete the tasks.</p><p>Shortly before the sprint, MITRE ATT&amp;CK released a new version of the framework with <a href="https://medium.com/mitre-attack/attack-with-sub-techniques-is-now-just-attack-8fc20997d8de">sub-techniques</a>. <a href="https://github.com/SigmaHQ/sigma/pull/989">We updated</a> the entire Sigma repository ruleset (reviewed 644 and updated 513 rules) with new MITRE ATT&amp;CK technique IDs (tags) in order to develop a detailed backlog.</p><p>We developed and published the <a href="https://oscd.community/sprints/sprint_2_backlog.html">backlog</a>, where for each task we specified the Estimated Time to Complete (ETC) and required knowledge. We also developed the <a href="https://oscd.community/sprints/sprint_2_howto.html">How-To</a> section, listing learning materials to get the required knowledge for every task. This way, participants could define the individual scope of tasks that they could realistically solve during the sprint, taking into account task description, amount of time they could spend on them, and their skillset.</p><p>We created Issues to the targeted projects’ repositories on GitHub based on the backlog. Maintainers created separate branches in the repositories for the OSCD, special thanks to them for this. Participants described the tasks in detail and gave all the background needed to solve them in those Issues, and also provided links to relevant research and resources, and to previous community work on each task. This helped to bring the work during the sprint as close as possible to real interactions within the open source community. Having gained such experience, it will be easier for the participants to further contribute to various projects after the end of the sprint.</p><p>We developed MITRE ATT&amp;CK® Navigator layers to visualize coverage of adversary techniques by threat detection rules (Sigma) and threat simulation tests (Atomic Red Team): one general <a href="https://mitre-attack.github.io/attack-navigator/enterprise/#layerURL=https%3A%2F%2Fraw.githubusercontent.com%2Foscd-initiative%2FOSCD_Sigma-ART_Layers%2Fmaster%2Fsigma-art-navigator-layer-windows.json">Sigma + ART</a> layer and separate layers for each operating system <a href="https://mitre-attack.github.io/attack-navigator/enterprise/#layerURL=https%3A%2F%2Fraw.githubusercontent.com%2Foscd-initiative%2FOSCD_Sigma-ART_Layers%2Fmaster%2Fsigma-art-navigator-layer-windows.json">Sigma + ART Windows</a> | <a href="https://mitre-attack.github.io/attack-navigator/enterprise/#layerURL=https%3A%2F%2Fraw.githubusercontent.com%2Foscd-initiative%2FOSCD_Sigma-ART_Layers%2Fmaster%2Fsigma-art-navigator-layer-linux.json">Sigma + ART GNU\Linux</a> | <a href="https://mitre-attack.github.io/attack-navigator/enterprise/#layerURL=https%3A%2F%2Fraw.githubusercontent.com%2Foscd-initiative%2FOSCD_Sigma-ART_Layers%2Fmaster%2Fart-navigator-layer-macos.json">ART macOS</a>.</p><p>The same way <a href="https://oscd-initiative.github.io/react-navigator/">we visualized</a> current and possible <a href="http://thehive-project.org/">TheHive</a> Analyzers and Responders coverage of the <a href="https://github.com/atc-project/atc-react">ATC RE&amp;CT</a> framework’s Response Actions.</p><p>The coverage visualizations of ATT&amp;CK and RE&amp;CT frameworks will help us estimate the real effect of our joint efforts.</p><h3>Beginning</h3><p>On 5th October 2020, <a href="https://twitter.com/oscd_initiative/status/1305748180517224449?s=20">the second OSCD sprint began</a> under the title “Simulation, Detection &amp; Response”. Unlike the first sprint, in which we focused only on threat detection, in the second sprint it was decided to give the participants the opportunity to demonstrate their knowledge in the field of attack emulation and incident response. Therefore, tasks for two other projects were added to the general backlog:</p><ul><li><strong>Atomic Red Team</strong> — small and highly portable detection tests based on MITRE’s ATT&amp;CK. It allows every security team to test their controls by executing simple “atomic tests” that exercise the same techniques used by adversaries. With time, Atomic Red Team tests set has become the biggest and the most mature community-driven Adversary Simulation tests set;</li><li><strong>TheHive</strong> — the most powerful open source and free Security Incident Response Platform. It has a module called<a href="https://thehive-project.org/#section_cortex"> Cortex</a> — Observable Analysis and Active Response Engine. It operates by two key entities, called Analyzers and Responders — simple Python scripts that utilize API to communicate with 3rd party systems and execute specific actions.</li></ul><h3>How it was</h3><p>We believe that the right choice of communication method during the sprint helps in the long run to build the right skills for working with open source repositories and communication within the community.</p><p>Therefore, during the sprint, participants communicated in Issues and Pull Requests to the targeted projects’ repositories on GitHub. We gave up chat rooms because they weren’t that useful last time. In spite of this, there were many good examples of open and productive communication. For example, while developing analytics <a href="https://github.com/SigmaHQ/sigma/pull/1033/files/c878d55ac0fd97d7f7fedebc3e15e4ad85326405#r501979040">to detect Lateral Movement techniques</a>, participants tagged <a href="https://twitter.com/HeirhabarovT">Teymur Kheirkhabarov</a>, the author of several studies on the topic, in a discussion on GitHub. He got in touch quickly and helped to find the solution.</p><p>Comments or corrections to other participants’ decisions were made in the form of suggestions, inviting them to consider or try a different approach. All suggestions were backed up by justification with specific examples and references.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*COPOykxspYZ2NvD0IIhliQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KgOLp21xvyfPcG06F5EJuQ.png" /><figcaption>Discussion examples</figcaption></figure><h3>Geography: 🇺🇸 🇷🇺 🇵🇱 🇹🇷 🇦🇺 🇨🇦 🇫🇷 🇮🇳 🇦🇪 🇦🇹 🇧🇷 🇩🇪 🇪🇸 🇳🇱 🇮🇱 🇭🇺 🇸🇬</h3><p>OSCD was designed as an international initiative and we are very inspired by the growing internationality of the initiative from sprint to sprint. This time there were <strong>triple</strong> as many specialists — 47 participants from 17 countries.</p><h3>Results</h3><p>The results exceeded all our expectations! The participants showed a high level of expertise and productivity. This is despite the increase in the number of projects! It is also worth noting the growth of the backlog size from sprint to sprint, while the indicators of the initiative’s total benefit for the community are steadily growing.</p><p>The sprint results were formalized as final Pull Requests in the corresponding projects. All in all, the participants achieved the following results:</p><ul><li>Developed 287 Sigma rules in total. 242 added and 305 updated by OSCD participants (<a href="https://github.com/SigmaHQ/sigma/pull/1362">Pull Request</a>). 45 rules added by <a href="https://twitter.com/otr_community">OTR Community</a> (<a href="https://github.com/SigmaHQ/sigma/pull/1158">Pull Request</a>);</li></ul><blockquote>It is second time we increased Sigma ruleset by more than 30%!</blockquote><ul><li>Developed 23 and updated 7 Atomic Red Team tests (<a href="https://github.com/redcanaryco/atomic-red-team/pull/1431">Pull Request</a>);</li><li>Developed 24 TheHive responders to automate response actions in Palo Alto NGFW, Duo Security, Gmail and Azure Active Directory (<a href="https://github.com/TheHive-Project/Cortex-Analyzers/pull/991">Pull Request</a>);</li><li>Developed 1 TheHive analyzer for IOC and CVE analysis with Vulners.com (<a href="https://github.com/TheHive-Project/Cortex-Analyzers/pull/880">Pull Request</a>).</li></ul><p>This is a good example of the results that can be achieved by the community working together to solve common problems. Practical cooperation, which we think we are lacking.</p><h3>Participants</h3><p>We express our deep gratitude to the specialists who took part in the last sprint. What is especially pleasant, that many of them participated for the second time. Here is the list of Sprint 2 participants, which is also <a href="https://oscd.community/index.html">available on our website</a>:</p><p>🇺🇸 Greg Howell | <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 <a href="https://twitter.com/Cyb3rPandaH">Jose Rodriguez</a>| <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 <a href="https://twitter.com/neu5ron">Nate Guagenti</a>| <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 Patrick St. John | <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 <a href="https://twitter.com/Cyb3rWard0g">Roberto Rodriguez</a> | <a href="https://twitter.com/OTR_Community">Open Threat Research</a><br>🇺🇸 <a href="https://twitter.com/craigtweets">Craig Young</a> | <a href="https://www.tripwire.com/">Tripwire</a><br>🇺🇸 <a href="https://twitter.com/danielweiner93">Daniel Weiner</a> | Independent Researcher<br>🇺🇸 Hare Sudhan Muthusamy | Independent Researcher<br>🇺🇸 <a href="https://twitter.com/remotephone">Jaime Flores</a> | Independent Researcher<br>🇺🇸 <a href="https://twitter.com/JohnLaTwC">John Lambert</a> | <a href="https://microsoft.com/">Microsoft</a><br>🇺🇸 <a href="https://twitter.com/tuckner">John Tuckner</a> | Independent Researcher<br>🇺🇸 <a href="https://twitter.com/WordPlas">Ryan Plas</a> | <a href="https://www.stage2sec.com/">Stage 2 Security</a><br>🇷🇺 Denis Beyu | Independent Researcher<br>🇷🇺 <a href="https://twitter.com/Dmitry_U4">Dmitry Uchakin</a> | <a href="https://www.kaspersky.com/">Kaspersky Lab</a>/<a href="https://vulners.com/">Vulners.com</a><br>🇷🇺 Igor Fits | Independent Researcher<br>🇷🇺 <a href="https://t.me/CatSchrodinger">Ilyas Ochkov</a> | Independent Researcher<br>🇷🇺 Maxim Konakin | Independent Researcher<br>🇷🇺 Natalia Shornikova | <a href="https://www.izsoc.ru/">IZ SOC</a><br>🇷🇺 <a href="https://twitter.com/HeirhabarovT">Teymur Kheirkhabarov</a> |<a href="https://www.bi.zone/"> BI.ZONE SOC</a><br>🇷🇺 <a href="https://twitter.com/vasebur">Vasiliy Burov</a> | Independent Researcher<br>🇵🇱 <a href="https://twitter.com/bczyz1">Bartlomiej Czyz</a> | Independent Researcher<br>🇵🇱 <a href="https://twitter.com/mrblacyk">Jakob Weinzettl</a><a href="https://twitter.com/mrblacyk"> </a>| <a href="https://www.tieto.com/en/what-we-do/managed-services-and-integration/security-services/security-operations-center/">Tieto SOC</a><br>🇵🇱 <a href="https://twitter.com/sn0w0tter">Mateusz Wydra</a> | <a href="https://www.relativity.com/ediscovery-software/relativityone/trust/threat-prevention/our-team/">Relativity</a><br>🇵🇱 <a href="https://twitter.com/aestimi">Tim Ismilyaev</a> | <a href="https://www.manasecurity.com/">Mana Security</a><br>🇹🇷 <a href="https://twitter.com/sblmsrsn">Ensar Şamil</a> | Independent Researcher<br>🇹🇷 <a href="https://twitter.com/caliskanfurkan_">Furkan Caliskan</a> | <a href="https://www.ziraatteknoloji.com/">Ziraat Teknoloji</a><br>🇹🇷 <a href="https://twitter.com/semanurtg">Semanur Guneysu</a> | <a href="https://www.destel.com.tr/">DESTEL / SOC</a><br>🇹🇷 <a href="https://twitter.com/ogunal00">Ömer Günal</a> | Independent Researcher<br>🇦🇺 <a href="https://twitter.com/CyberRaiju">Jai Minton</a> | Independent Researcher<br>🇦🇺 Jonathan Cheong | Independent Researcher<br>🇦🇺 <a href="https://twitter.com/svch0st">Zach Stanford</a> | <a href="https://twitter.com/CxCyber">CyberCX</a><br>🇨🇦 <a href="https://twitter.com/v3t0_">Avneet Singh</a> | Independent Researcher<br>🇨🇦 <a href="https://twitter.com/tas_kmanager">Mangatas Tondang</a> | Independent Researcher<br>🇫🇷 <a href="https://twitter.com/gregclermont">Grégoire Clermont</a> | Independent Researcher<br>🇫🇷 <a href="https://twitter.com/nadouani">Nabil Adouani</a> | <a href="https://thehive-project.org/">TheHive</a>/<a href="https://www.strangebee.com/">StrangeBee</a><br>🇮🇳 <a href="https://twitter.com/iamkirankmr">Kiran Kumar</a> | Independent Researcher<br>🇮🇳 <a href="https://twitter.com/OG0Sec">Omkar Gudhate</a> | Independent Researcher<br>🇦🇪 <a href="https://twitter.com/stvetro">Victor Sergeev</a> | <a href="https://www.helpag.com/">Help AG</a><br>🇦🇹 <a href="https://twitter.com/strassi7">David Straßegger</a> | Independent Researcher<br>🇧🇷 <a href="https://twitter.com/_w0rk3r">Jonhnathan Ribeiro</a> | Independent Researcher<br>🇩🇪 <a href="https://twitter.com/blubbfiction">Thomas Patzke</a> | <a href="https://github.com/SigmaHQ/sigma">Sigma Project</a><br>🇪🇸 <a href="https://twitter.com/aomanzanera">Alejandro Ortuno</a> | Independent Researcher<br>🇭🇺 <a href="https://twitter.com/AcsGacs">Gyorgy Acs</a> |<a href="https://cisco.com/"> Cisco</a><br>🇮🇱 Eli Salem | Independent Researcher<br>🇳🇱 Sander Wiebing | <a href="https://www.nfir.nl/">NFIR B.V.</a><br>​​🏳<a href="https://twitter.com/yugoslavskiy">️ Daniil Yugoslavsk</a>iy | <a href="https://twitter.com/atc_project">Atomic Threat Coverage</a><br>🇸🇬 Gleb Sukhodolskiy | Independent Researcher</p><p>Thank you all!</p><p>BTW, we’ve created a <a href="https://www.linkedin.com/company/oscd-initiative/">LinkedIn organization</a>, so you can mention your Sprints participation as a volunteer experience:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MoIIp-K7VcfoccuYzr7FmQ.png" /></figure><h3>Want to be involved</h3><p>Do you also want to make the world a little safer and apply your knowledge for the greater good? OSCD has no entry requirements. The work is done openly and solely for the benefit of the community, not for profit and without any relations to commercial organizations. Follow the news on <a href="https://twitter.com/oscd_initiative">Twitter</a> or in <a href="https://t.me/oscd_initiative">Telegram</a>, wait for the next sprint announcement, choose a task from the backlog or propose your own, and develop a solution together with the community!</p><h3>Useful links</h3><ul><li>Our<a href="https://oscd.community/"> website</a></li><li>Our <a href="https://twitter.com/oscd_initiative">twitter</a>; mirror in <a href="https://t.me/oscd_initiative">telegram</a></li><li><a href="https://twitter.com/i/lists/1308954210470428672">OSCD Participants Twitter list</a></li></ul><blockquote><em>Original publication date — September 10, 2021</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43fd9298128c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oscd/oscd-sprint-2-detection-simulation-response-results-43fd9298128c">OSCD Sprint # 2: Detection, Simulation &amp; Response, results (EN)</a> was originally published in <a href="https://medium.com/oscd">OSCD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSCD: Threat Detection Sprint #1, results (EN)]]></title>
            <link>https://medium.com/oscd/oscd-threat-detection-sprint-1-results-en-a78742d2e67a?source=rss----bfea556c7193---4</link>
            <guid isPermaLink="false">https://medium.com/p/a78742d2e67a</guid>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[threat-detection]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <dc:creator><![CDATA[Open Security Collaborative Development]]></dc:creator>
            <pubDate>Mon, 18 Apr 2022 21:41:12 GMT</pubDate>
            <atom:updated>2022-04-20T06:00:42.854Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Figures for 6 of December 2019, when final PR from OSCD to Sigma master branch has been created" src="https://cdn-images-1.medium.com/max/1024/1*a7jvv92A-uCb0XBeUeG14Q.png" /><figcaption>Figures for 6 of December 2019, when final PR from OSCD to Sigma master branch has been created</figcaption></figure><blockquote><em>Original publication date — December 31, 2019</em></blockquote><p>Open Security Collaborative Development (OSCD) is an open international cybersecurity specialist initiative. We collaborate on common problems and share knowledge.</p><p>It was created fall 2019 by friendly open source security projects. The collaborative development is organized as two weeks-long sprints.<br>The First Sprint focused on the Threat Detection area and Sigma Project ruleset specifically.</p><h3>Why Sigma</h3><p><a href="https://github.com/Neo23x0/sigma/">Sigma Project</a> is Generic Signature Format for SIEM Systems. It has a converter that generates searches/queries for different SIEM systems and a set of Detection Rules, which converter uses for queries generation.</p><p>With time, Sigma Project ruleset has become the biggest and the most mature community-driven Detection Rules set. This is the place where you could find Detection Rules for emerging threats (like <a href="https://github.com/Neo23x0/sigma/blob/master/rules/windows/builtin/win_rdp_potential_cve-2019-0708.yml">BlueKeep</a> exploits), adversary simulations tools (<a href="https://github.com/Neo23x0/sigma/search?q=empire&amp;unscoped_q=empire">Empire</a>, <a href="https://github.com/Neo23x0/sigma/search?q=cobalt+strike&amp;unscoped_q=cobalt+strike">Cobalt Strike</a>), adversary behaviors (<a href="https://github.com/Neo23x0/sigma/blob/master/rules/windows/process_creation/win_kernel_and_3rd_party_drivers_exploits_token_stealing.yml">Token stealing</a>), and many more. Most of the rules are mapped to the <a href="https://attack.mitre.org/">MITRE ATT&amp;CK</a>.</p><p>Even if you are not using Sigma converter, you still can benefit from its ruleset. Most of the advanced security teams are subscribed to the Sigma Project updates on <a href="https://github.com/Neo23x0/sigma/">GitHub</a>. It’s a good time to do so if you haven’t yet.</p><p>There are some gaps and issues in it, at the same time, there is plenty of decent analytics published (i.e. researches on Hunting for <a href="https://www.slideshare.net/heirhabarov/hunting-for-privilege-escalation-in-windows-environment">Windows Privilege Escalation</a> / <a href="https://drive.google.com/file/d/1lKya3_mLnR3UQuCoiYruO3qgu052_iS_/view?usp=sharing">Lateral Movement</a> / <a href="https://www.slideshare.net/heirhabarov/hunting-for-credentials-dumping-in-windows-environment">Credentials Dumping</a> tools and techniques) that haven’t been added to Sigma Project repository. This is the thing we’ve decided to focus on during The First Sprint.</p><h3>How it was</h3><p>About 50 individuals confirmed that they will join the the sprint. The plan was simple:</p><ol><li>Two weeks-long sprint starts October 21, 2019</li><li>Participants pick up tasks from the <a href="https://docs.google.com/document/d/1aAIZr4TKwF94zzVi44tAPs-HLJRg1Nz62GZr4oIXoEA">backlog</a> or contribute other analytics</li><li>Participants use the <a href="https://docs.google.com/document/d/1EGKfXwlea-Nf1TwqZH09dqPjerDbo6PFyt9DpX0daRk">guideline</a> to get familiar with the workflow</li><li>Results reviewed and pushed to Sigma repository on GitHub</li></ol><p>A few days after the start, 24 of October, we’ve conducted a <a href="https://cfp.hack.lu/hacklu19/talk/BEEXFL/">workshop</a> at the hack.lu conference, presented the OSCD, explained what we were doing and why. Although most of the participants were joining remotely, it was quite fruitful time, as we were able to sit next to each other and discuss the rules.</p><p>Next day we’ve reported the first results on <a href="https://www.youtube.com/watch?v=lkkC4UEIpAE&amp;feature=youtu.be&amp;t=438">EU MITRE ATT&amp;CK workshop</a> in Luxembourg:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O2ouu9fAB00t78ojVc7ZlQ.png" /></figure><p>And we’ve achieved the expected results, even though by the end of the sprint the number of participants dropped to 16.</p><h3>Results</h3><p>During the two-weeks long sprint we have:</p><ul><li>Developed 144 Sigma rules</li><li>Improved 19 existing rules and deprecated 2</li></ul><blockquote>This way, we increased Sigma ruleset by <strong>more than 40%!</strong></blockquote><p>The listing of contributed rules is available in the description of the <a href="https://github.com/Neo23x0/sigma/pull/554">Pull Request</a> in the Sigma project repository.</p><h3>Backlog</h3><p>Even though we achieved a lot during the first sprint, there are many things that we were not able to manage in two weeks. We decided to detail the backlog and put it into the Sigma Repo issues for the community to pick up:</p><ul><li><a href="https://github.com/Neo23x0/sigma/issues/574">Develop Sigma rules for Privilege Escalation in Windows Environment</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/575">Develop Sigma rules for PowerShell Abuse</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/576">Develop Sigma rules for Lateral Movement in Windows Infrastructure</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/577">Develop Sigma rules for Invoke-DOSfuscation</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/578">Develop Sigma rules for Invoke-Obfuscation</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/579">Develop Sigma rules for Living Off The Land Binaries and Scripts</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/580">Develop Sigma rules for Atomic Red Team tests</a></li></ul><p>We believe that community collaboration to solve the listed (and others, but the same kind) tasks is the most realistic and fast solution to the problem of the “Offensive Security Tools release”, that is under <a href="https://medium.com/@QW5kcmV3/misconceptions-unrestricted-release-of-offensive-security-tools-789299c72afe">heavy</a> <a href="http://lockboxx.blogspot.com/2019/12/misconceptions-regarding-offensive.html?view=flipcard">discussion</a> for the last weeks.</p><p>We are aiming to have Detection Rules covering TTP level by <a href="https://globalsecuresolutions.com/the-pyramid-of-pain/">The Pyramid of Pain</a>, this way we would be able to detect adversary <em>behaviors</em>, regardless of the tool. ‘Offensive Security Tools’ are our best friends in this area.</p><h3>Acknowledgment</h3><p>The First OSCD sprint wouldn’t happen without <a href="https://twitter.com/adulau">Alexandre Dulaunoy</a> and the team of <a href="https://2019.hack.lu/">hack.lu</a> conference organizers. They have provided a timeslot at the conference for the OSCD workshop; visa, accommodation, and informational support. We are very grateful for that.</p><p>Last but not least, it wouldn’t happen without the participants who have done all the hard work:</p><p>🇩🇪 Eva Maria Anhaus | <a href="https://www.bsi-fuer-buerger.de/">BSI</a><br>🇩🇪 Jan Hasenbusch | <a href="https://www.bsi-fuer-buerger.de/">BSI</a><br>🇩🇪 <a href="https://twitter.com/blubbfiction">Thomas Patzke</a> | <a href="https://github.com/Neo23x0/sigma/">Sigma Projec</a>t<br>🇷🇺 Denis Beyu | Independent Researcher<br>🇷🇺 <a href="https://t.me/CatSchrodinger">Ilyas Ochkov</a> | Independent Researcher<br>🇷🇺 <a href="https://twitter.com/HeirhabarovT">Teymur Kheirkhabarov</a> | <a href="https://www.bi.zone/">BI.ZONE SOC</a><br>🇵🇱 <a href="https://twitter.com/mrblacyk">Jakob Weinzettl</a> | <a href="https://www.tieto.com/en/what-we-do/managed-services-and-integration/security-services/security-operations-center/">Tieto SOC</a><br>🇵🇱 <a href="https://twitter.com/sn0w0tter">Mateusz Wydra</a> | <a href="https://www.relativity.com/ediscovery-software/relativityone/trust/threat-prevention/our-team/">Relativity</a><br>🇦🇪 <a href="https://twitter.com/stvetro">Victor Sergeev</a> | <a href="https://www.helpag.com/">Help AG</a><br>🇦🇷 <a href="https://twitter.com/darkquassar">Diego Perez</a> | Independent Researcher<br>🇦🇺 <a href="https://twitter.com/4A616D6573">James Pemberton</a> | <a href="https://www.hydro.com.au/">Hydro Tasmania</a><br>🇨🇿 Ian Davis | <a href="https://www.tieto.com/en/what-we-do/managed-services-and-integration/security-services/security-operations-center/">Tieto SOC</a><br>🏳️ <a href="https://twitter.com/yugoslavskiy">Daniil Yugoslavskiy</a> | <a href="https://twitter.com/atc_project">Atomic Threat Coverage</a><br>🇸🇬 Gleb Sukhodolskiy | Independent Researcher<br>🇸🇮 Tom Kern | <a href="https://www.nil.com/en/security/security-operations-center-soc-building-services/">NIL SOC</a><br>🇺🇸 <a href="https://twitter.com/danielhbohannon">Daniel Bohannon</a> | <a href="https://www.fireeye.com/services.html">FireEye</a></p><p>Thank you all. See you <a href="https://oscd.community/sprints/sprint_2.html">next sprint</a>!</p><h3>Want to be involved</h3><p>Do you also want to make the world a little safer and apply your knowledge for the greater good? OSCD has no entry requirements. The work is done openly and solely for the benefit of the community, not for profit and without any relations to commercial organizations. Follow the news on <a href="https://twitter.com/oscd_initiative">Twitter</a> or in <a href="https://t.me/oscd_initiative">Telegram</a>, wait for the next sprint announcement, choose a task from the backlog or propose your own, and develop a solution together with the community!</p><h3>Useful links</h3><ul><li>Our<a href="https://oscd.community/"> website</a></li><li>Our <a href="https://twitter.com/oscd_initiative">twitter</a>; mirror in <a href="https://t.me/oscd_initiative">telegram</a></li><li><a href="https://twitter.com/i/lists/1308954210470428672">OSCD Participants Twitter list</a></li></ul><blockquote><em>Original publication date — December 31, 2019</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a78742d2e67a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oscd/oscd-threat-detection-sprint-1-results-en-a78742d2e67a">OSCD: Threat Detection Sprint #1, results (EN)</a> was originally published in <a href="https://medium.com/oscd">OSCD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSCD: Threat Detection Sprint #1, итоги (RU)]]></title>
            <link>https://medium.com/oscd/oscd-threat-detection-sprint-1-%D0%B8%D1%82%D0%BE%D0%B3%D0%B8-ru-3b3a9f643278?source=rss----bfea556c7193---4</link>
            <guid isPermaLink="false">https://medium.com/p/3b3a9f643278</guid>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-detection]]></category>
            <dc:creator><![CDATA[Open Security Collaborative Development]]></dc:creator>
            <pubDate>Mon, 18 Apr 2022 21:09:35 GMT</pubDate>
            <atom:updated>2022-04-20T05:53:38.462Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Числа на 6 Декабря 2019, когда был создан итоговый Pull Request в ветку master проекта Sigma" src="https://cdn-images-1.medium.com/max/1024/1*PwvuxrmRCAhKaB-4LzHS1A.jpeg" /><figcaption>Числа на 6 Декабря 2019, когда был создан итоговый Pull Request в ветку master проекта Sigma</figcaption></figure><blockquote>Оригинальная дата публикации — 31.12.2019</blockquote><p>Open Security Collaborative Development — это открытая международная инициатива специалистов по компьютерной безопасности. Мы совместно решаем общие проблемы и распространяем знания.</p><p>Инициатива была создана осенью 2019 года дружественными свободными проектами из сферы информационной безопасности. Совместная разработка организуется в виде двухнедельных спринтов. Первый спринт был посвящен обнаружению угроз в целом и улучшению набора правил проекта Sigma в частности.</p><h3>Почему Sigma</h3><p>Проект <a href="https://github.com/SigmaHQ/sigma">Sigma</a> — это общий формат сигнатур для SIEM систем. Он представляет собой конвертор, который генерирует поисковые запросы для различных SIEM систем и открытый набор правил обнаружения, из которых эти запросы генерируются.</p><p>Со временем набор правил проекта Sigma стал самым большим и зрелым набором правил обнаружения угроз, управляемым сообществом. В нем вы можете найти правила обнаружения угроз (правила “корреляции”) для новых угроз (например эксплойты для <a href="https://github.com/Neo23x0/sigma/blob/master/rules/windows/builtin/win_rdp_potential_cve-2019-0708.yml">BlueKeep</a>), инструментов для проведения тестирования на проникновение (<a href="https://github.com/Neo23x0/sigma/search?q=empire&amp;unscoped_q=empire">Empire</a>, <a href="https://github.com/Neo23x0/sigma/search?q=cobalt+strike&amp;unscoped_q=cobalt+strike">Cobalt Strike</a>), вредоносного поведения (<a href="https://github.com/Neo23x0/sigma/blob/master/rules/windows/process_creation/win_kernel_and_3rd_party_drivers_exploits_token_stealing.yml">Token stealing</a>), и многое другое. Большинство правил имеют привязку к <a href="https://attack.mitre.org/">MITRE ATT&amp;CK</a>.</p><p>Даже если вы не используете конвертор Sigma, вы можете извлечь выгоду из его обновляемого набора правил обнаружения угроз. Большинство продвинутых команд по безопасности подписаны на обновления проекта Sigma на <a href="https://github.com/SigmaHQ/sigma">GitHub</a>. Это отличное время, чтобы подписаться, если вы этого еще не сделали.</p><p>В этом проекте есть пробелы и проблемы, в то же время в публичном доступе существует множество достойных исследований (таких как Hunting for <a href="https://www.slideshare.net/heirhabarov/hunting-for-privilege-escalation-in-windows-environment">Windows Privilege Escalation</a> / <a href="https://drive.google.com/file/d/1lKya3_mLnR3UQuCoiYruO3qgu052_iS_/view">Lateral Movement</a> / <a href="https://www.slideshare.net/heirhabarov/hunting-for-credentials-dumping-in-windows-environment">Credentials Dumping</a>), материалы которых пока не были добавлены в репозиторий проекта. Это то, на чем мы решили сосредоточиться в ходе первого спринта.</p><h3>Как это было</h3><p>Около 50 человек подтвердили свое участие. План был прост:</p><ol><li>Двухнедельный спринт начинается 21 Октября 2019</li><li>Участники выбирают задачи из <a href="https://docs.google.com/document/u/1/d/1aAIZr4TKwF94zzVi44tAPs-HLJRg1Nz62GZr4oIXoEA">беклога</a> или предоставляют/разрабатывают иную аналитику</li><li>Участники опираются на <a href="https://docs.google.com/document/d/1EGKfXwlea-Nf1TwqZH09dqPjerDbo6PFyt9DpX0daRk">руководство</a> с описанием рабочего процесса</li><li>Результаты будут проверены и добавлены в репозиторий проекта Sigma на <a href="https://github.com/SigmaHQ/sigma">GitHub</a></li></ol><p>Через несколько дней, 24 Октября 2019, мы провели <a href="https://cfp.hack.lu/hacklu19/talk/BEEXFL/">воркшоп</a> на конференции hack.lu, презентовали инициативу, объяснили что мы делаем и зачем. Хотя большинство участников подключалось к работе удаленно, мы очень плодотворно провели время на воркшопе, поскольку можно было обсуждать разрабатываемые правила в режиме живой дискуссии.</p><p>На следующий день мы отчитались о промежуточных результатах на <a href="https://www.youtube.com/watch?v=lkkC4UEIpAE&amp;feature=youtu.be&amp;t=438">воркшопе EU MITRE ATT&amp;CK</a> в Люксембурге:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O2ouu9fAB00t78ojVc7ZlQ.png" /></figure><p>И мы достигли ожидаемого результата (x2), несмотря на то что в конце спринта реальное количество участников сократилось до 16 человек.</p><h3>Результат</h3><p>В течение двухнедельного спринта мы:</p><ul><li>Разработали 144 правила Sigma</li><li>Улучшили 19 существующих правил, и удалили 2</li></ul><blockquote>Таким образом, мы увеличили набор правил проекта Sigma более чем на 40%!</blockquote><p>Список добавленных правил доступен в описании <a href="https://github.com/Neo23x0/sigma/pull/554">Pull Request</a> в мастер ветку репозитория Sigma на GitHub.</p><h3>Бэклог</h3><p>Хотя мы и добились многого за первый спринт, осталось множество задач, которые было невозможно решить нашими силами в течение двух недель. Мы решили детализировать бэклог и перенести его в issues репозитория Sigma для последующей их обработки силами сообщества:</p><ul><li><a href="https://github.com/Neo23x0/sigma/issues/574">Develop Sigma rules for Privilege Escalation in Windows Environment</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/575">Develop Sigma rules for PowerShell Abuse</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/576">Develop Sigma rules for Lateral Movement in Windows Infrastructure</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/577">Develop Sigma rules for Invoke-DOSfuscation</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/578">Develop Sigma rules for Invoke-Obfuscation</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/579">Develop Sigma rules for Living Off The Land Binaries and Scripts</a></li><li><a href="https://github.com/Neo23x0/sigma/issues/580">Develop Sigma rules for Atomic Red Team tests</a></li></ul><p>Мы убеждены, что совместное решение перечисленных (и иных, того же рода) задач — это наиболее реалистичное и быстрое решение проблемы публикации “Offensive Security Tools”, которая <a href="https://medium.com/@QW5kcmV3/misconceptions-unrestricted-release-of-offensive-security-tools-789299c72afe">бурно</a> <a href="http://lockboxx.blogspot.com/2019/12/misconceptions-regarding-offensive.html?view=flipcard">обсуждается</a> последние недели.</p><p>Мы стремимся, чтобы наши Правила Обнаружения покрывали уровень TTP по модели <a href="https://globalsecuresolutions.com/the-pyramid-of-pain/">The Pyramid of Pain</a>, таким образом, мы сможем детектировать вредоносное <em>поведение</em>, безотносительно используемого инструмента. ‘Offensive Security Tools’ — наши лучшие друзья в исследованиях и разработке правил такого типа.</p><h3>Благодарности</h3><p>Первый OSCD Спринт не состоялся бы без <a href="https://twitter.com/adulau">Александре Дюлонуа</a> и команды организаторов конференции <a href="https://2019.hack.lu/">hack.lu</a>. Они предоставили информационную поддержку, слот на конференции для воркшопа OSCD, помогли с получением визы и проживанием. Мы очень благодарны им за это.</p><p>Последнее, но не менее важное — участники спринта:</p><p>🇩🇪 Ева Мария Анхауз | <a href="https://www.bsi-fuer-buerger.de/">BSI</a><br>🇩🇪 Ян Хазенбуш | <a href="https://www.bsi-fuer-buerger.de/">BSI</a><br>🇩🇪 <a href="https://twitter.com/blubbfiction">Томас Пацке</a> | <a href="https://github.com/Neo23x0/sigma/">Sigma Project</a><br>🇷🇺 Денис Бею | Независимый Исследователь<br>🇷🇺 <a href="https://t.me/CatSchrodinger">Ильяс Очков</a> | Независимый Исследователь<br>🇷🇺 <a href="https://twitter.com/HeirhabarovT">Теймур Хеирхабаров</a> | <a href="https://www.bi.zone/">BI.ZONE SOC</a><br>🇵🇱 <a href="https://twitter.com/mrblacyk">Якоб Вайнзетл</a> | <a href="https://www.tieto.com/en/what-we-do/managed-services-and-integration/security-services/security-operations-center/">Tieto SOC</a><br>🇵🇱 <a href="https://twitter.com/sn0w0tter">Матэуш Выдра</a> | <a href="https://www.relativity.com/ediscovery-software/relativityone/trust/threat-prevention/our-team/">Relativity</a><br>🇦🇪 <a href="https://twitter.com/stvetro">Виктор Сергеев</a> | <a href="https://www.helpag.com/">Help AG</a><br>🇦🇷 <a href="https://twitter.com/darkquassar">Диего Перез</a> | Независимый Исследователь<br>🇦🇺 <a href="https://twitter.com/4A616D6573">Джеймс Пембетон</a> | <a href="https://www.hydro.com.au/">Hydro Tasmania</a><br>🇨🇿 Иэн Дэвис | <a href="https://www.tieto.com/en/what-we-do/managed-services-and-integration/security-services/security-operations-center/">Tieto SOC</a><br>🏳️ <a href="https://twitter.com/yugoslavskiy">Даниил Югославский</a> | <a href="https://twitter.com/atc_project">Atomic Threat Coverage</a><br>🇸🇬 Глеб Суходольский | Независимый Исследователь<br>🇸🇮 Том Керн | <a href="https://www.nil.com/en/security/security-operations-center-soc-building-services/">NIL SOC</a><br>🇺🇸 <a href="https://twitter.com/danielhbohannon">Дэниэл Бохэннон</a> | <a href="https://www.fireeye.com/services.html">FireEye</a></p><p>Спасибо вам! Увидимся на <a href="https://oscd.community/sprints/sprint_2.html">следующем спринте</a>!</p><h3>Хочу участвовать</h3><p>В OSCD нет входных требований для участников. Работа ведется открыто и исключительно в интересах сообщества, не для обогащения и без связей с коммерческими организациями.<br>Следите за новостями в <a href="https://twitter.com/oscd_initiative">Twitter</a> или в <a href="https://t.me/oscd_initiative">Telegram</a>, дождитесь объявления о начале следующего спринта, выберите себе задачу из бэклога или предложите свою, и разработайте решение вместе с сообществом!</p><h3>Полезные ссылки</h3><ul><li>Наш <a href="https://oscd.community/">вебсайт</a></li><li>Наш <a href="https://twitter.com/oscd_initiative">twitter</a>; зеркало в <a href="https://t.me/oscd_initiative">telegram</a></li><li><a href="https://twitter.com/i/lists/1308954210470428672">List участников OSCD в Twitter</a></li></ul><blockquote>Оригинальная дата публикации — 31.12.2019</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b3a9f643278" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oscd/oscd-threat-detection-sprint-1-%D0%B8%D1%82%D0%BE%D0%B3%D0%B8-ru-3b3a9f643278">OSCD: Threat Detection Sprint #1, итоги (RU)</a> was originally published in <a href="https://medium.com/oscd">OSCD</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>