<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How should we position  AMP &amp; CTA together in Endpoint Security</title>
    <link>https://community.cisco.com/t5/endpoint-security/how-should-we-position-amp-cta-together/m-p/3434399#M1748</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for being so late to reply ... just a few thoughts, and I'll try to keep this short.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each piece of our architectural security portfolio has a unique view and therefore, as you say, each piece will catch things that another might miss.&amp;nbsp; Most people these days understand that no single tool can be 100% right 100% of the time.&amp;nbsp; An important corollary to that basic fact of life is this: some malware &lt;EM&gt;will&lt;/EM&gt; get inside the network, and we &lt;EM&gt;must&lt;/EM&gt; design our solutions for that reality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the case of AMP, that means first &lt;STRONG&gt;prevention&lt;/STRONG&gt;, and then &lt;STRONG&gt;retrospection&lt;/STRONG&gt;; we do our best (and independent tests indicate that we're doing pretty well) to catch things up front, using a combination of detection, analysis (Threat Grid), and intelligence (Talos), but we also keep track of everything we see, no matter what the disposition. That way, when things inevitably change, we're prepared.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cognitive (CTA) provides a valuable addition, because it focuses on a separate source of telemetry (web proxy logs) and focuses on advanced machine learning for &lt;STRONG&gt;anomaly detection&lt;/STRONG&gt;, part of the larger field of breach detection and response. As of a few months ago, all AMP for Endpoints customers have the option of feeding their proxy logs to CTA, with indications of compromise from CTA integrated into the AMP cloud console.&amp;nbsp; This allows you to do things like detect previously unknown command and control (C&amp;amp;C) channels.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This response is necessarily high level -- a complete answer could fill many pages -- but I hope it is of some use.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Aug 2016 07:24:06 GMT</pubDate>
    <dc:creator>brmcmaho</dc:creator>
    <dc:date>2016-08-30T07:24:06Z</dc:date>
    <item>
      <title>How should we position  AMP &amp; CTA together</title>
      <link>https://community.cisco.com/t5/endpoint-security/how-should-we-position-amp-cta-together/m-p/3434398#M1722</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings!&lt;/P&gt;&lt;P&gt;Please help ,as how should we position&amp;nbsp; AMP &amp;amp; CTA together to any customer which could generate their interest on both (how utilizing CTA with AMP can further enhance their security), like anything which AMP missed is caught by CTA.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:01:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/endpoint-security/how-should-we-position-amp-cta-together/m-p/3434398#M1722</guid>
      <dc:creator>Rohitashva Verma</dc:creator>
      <dc:date>2020-02-21T05:01:36Z</dc:date>
    </item>
    <item>
      <title>Re: How should we position  AMP &amp; CTA together</title>
      <link>https://community.cisco.com/t5/endpoint-security/how-should-we-position-amp-cta-together/m-p/3434399#M1748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for being so late to reply ... just a few thoughts, and I'll try to keep this short.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each piece of our architectural security portfolio has a unique view and therefore, as you say, each piece will catch things that another might miss.&amp;nbsp; Most people these days understand that no single tool can be 100% right 100% of the time.&amp;nbsp; An important corollary to that basic fact of life is this: some malware &lt;EM&gt;will&lt;/EM&gt; get inside the network, and we &lt;EM&gt;must&lt;/EM&gt; design our solutions for that reality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the case of AMP, that means first &lt;STRONG&gt;prevention&lt;/STRONG&gt;, and then &lt;STRONG&gt;retrospection&lt;/STRONG&gt;; we do our best (and independent tests indicate that we're doing pretty well) to catch things up front, using a combination of detection, analysis (Threat Grid), and intelligence (Talos), but we also keep track of everything we see, no matter what the disposition. That way, when things inevitably change, we're prepared.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cognitive (CTA) provides a valuable addition, because it focuses on a separate source of telemetry (web proxy logs) and focuses on advanced machine learning for &lt;STRONG&gt;anomaly detection&lt;/STRONG&gt;, part of the larger field of breach detection and response. As of a few months ago, all AMP for Endpoints customers have the option of feeding their proxy logs to CTA, with indications of compromise from CTA integrated into the AMP cloud console.&amp;nbsp; This allows you to do things like detect previously unknown command and control (C&amp;amp;C) channels.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This response is necessarily high level -- a complete answer could fill many pages -- but I hope it is of some use.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Aug 2016 07:24:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/endpoint-security/how-should-we-position-amp-cta-together/m-p/3434399#M1748</guid>
      <dc:creator>brmcmaho</dc:creator>
      <dc:date>2016-08-30T07:24:06Z</dc:date>
    </item>
  </channel>
</rss>

