<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: bot365</title>
    <description>The latest articles on DEV Community by bot365 (@bot365).</description>
    <link>https://dev.to/bot365</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F256407%2F7695242e-0aa3-41d7-abd6-0b3a45e5a351.jpg</url>
      <title>DEV Community: bot365</title>
      <link>https://dev.to/bot365</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bot365"/>
    <language>en</language>
    <item>
      <title>AWS Threat Detection Overview</title>
      <dc:creator>bot365</dc:creator>
      <pubDate>Sun, 25 Oct 2020 13:00:14 +0000</pubDate>
      <link>https://dev.to/bot365/aws-threat-detection-overview-19c4</link>
      <guid>https://dev.to/bot365/aws-threat-detection-overview-19c4</guid>
      <description>&lt;p&gt;&lt;strong&gt;AWS Threat Detection Service&lt;/strong&gt;:&lt;br&gt;
Amazon GuardDuty is threat detection service that continuously monitors for malicious activity and it keeps track of unauthorized API activity or behavior to protect AWS accounts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How GuardDuty works&lt;/strong&gt;:&lt;/p&gt;

&lt;p&gt;Once we enable the GuradDuty within our AWS account, it automatically start collecting VPC flow logs,Cloudtrail logs event(Management and Data event) and DNS query logs. It continuously monitor and analyze these logs and provide us the findings If there is any abnormal activity within AWS account.&lt;/p&gt;

&lt;p&gt;It also uses threat intelligence feeds, such as lists of malicious IP addresses and domains, and machine learning to identify unauthorized and malicious activity within our AWS environment.&lt;/p&gt;

&lt;p&gt;Along with AWS threat intelligence feeds we can use our own Blacklist and Whitelist IP address for malicious IP detection.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--_inIVS-d--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/0y9ke3hj7ku7byrv023t.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--_inIVS-d--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/0y9ke3hj7ku7byrv023t.png" alt="Alt Text"&gt;&lt;/a&gt;&lt;br&gt;
(Image taken from AWS)&lt;br&gt;
&lt;strong&gt;How to enable GuardDuty in AWS Account&lt;/strong&gt;:&lt;/p&gt;

&lt;p&gt;When we enable GuardDuty for the first time, AWS account is automatically enrolled in a &lt;strong&gt;30-day&lt;/strong&gt; GuardDuty free trial. We can view the details of GuardDuty free trial in the usage page of the GuardDuty console.&lt;br&gt;
Steps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Login to the console, choose the region and find GuardDuty under 
Services.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s---nMCqlE1--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/96l8vvyju1yfrckg5pnl.PNG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s---nMCqlE1--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/96l8vvyju1yfrckg5pnl.PNG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;After clicking on GuardDuty, below page will be display. Click 
on Get started.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--864FoO-0--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/30c4jwbskoc93z4y1tmz.PNG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--864FoO-0--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/30c4jwbskoc93z4y1tmz.PNG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt; Click on Enable GuardDuty. When GuardDuty is enabled a 
GuardDuty detector is created in that region.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When we enable GuardDuty, it create service-linked  role called &lt;br&gt;
   AWSServiceRoleForAmazonGuardDuty. This service-linked role &lt;br&gt;
   allows GuardDuty to retrieve details of EC2 instances and S3 &lt;br&gt;
   buckets in our AWS environment that are involved in potentially &lt;br&gt;
   suspicious activity.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--PV0__L39--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/vq55ftzqx5uwr3ig0nrn.PNG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--PV0__L39--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/vq55ftzqx5uwr3ig0nrn.PNG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;After enabling GuardDuty, it takes some time to display the 
findings.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--ixAk_1JQ--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/a2xotea2kqwkrk1gqxxa.PNG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--ixAk_1JQ--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/a2xotea2kqwkrk1gqxxa.PNG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to check GuardDuty Findings:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Go to GuardDuty&amp;gt; Findings. Below is screenshot of sample 
findings.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--G1FkcJAg--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/kz7e47w2ncqmbwbekxsv.PNG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--G1FkcJAg--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/kz7e47w2ncqmbwbekxsv.PNG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to create Custom Whitelist and Blacklist IP lists.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Go to GuardDuty&amp;gt; Settings&amp;gt; lists&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--7Lhfq7GI--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/19flqdlfblucf5qtztml.PNG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--7Lhfq7GI--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/19flqdlfblucf5qtztml.PNG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;To add trusted IPs(Whitelist), click on add trusted IP list. If 
you would like to add custom Blacklist IPs, click on add a 
threat list.
After clicking on "add a trusted IP list/add a threat list" It 
will prompt and ask us to specify the bucket URL where we are 
storing blacklist and whitelist IP address. Please refer below 
screenshot.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--cHcYNWSk--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/whm1r333l4jpobwbs23r.PNG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--cHcYNWSk--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/whm1r333l4jpobwbs23r.PNG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--1CD7e5AB--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/9bkged4ocdebdq7ybrtw.PNG" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--1CD7e5AB--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/9bkged4ocdebdq7ybrtw.PNG" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Severity levels for GuardDuty findings&lt;/strong&gt;:&lt;/p&gt;

&lt;p&gt;Each GuardDuty finding has severity level and value range. Severity value range start from 0 to 10.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  High (7.0 - 8.9)&lt;/li&gt;
&lt;li&gt;  Medium (4 - 6.9)&lt;/li&gt;
&lt;li&gt;  Low (1 -3.9 )&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Where is severity value 0-0.9 and 9.0-10.0?&lt;/p&gt;

&lt;p&gt;Values 0 and 9.0 to 10.0 are currently reserved for future use by AWS.&lt;/p&gt;

&lt;p&gt;By default findings are automatically sent to CloudWatch Events&lt;br&gt;
every 6 hours and it can be change to 1 hour and 15 minutes.&lt;br&gt;
GuardDuty can also send findings to S3 bucket and that can be further use for analysis and take action by third party tools.&lt;/p&gt;

&lt;p&gt;Thank You.&lt;/p&gt;

</description>
      <category>security</category>
      <category>aws</category>
      <category>cloud</category>
    </item>
  </channel>
</rss>
