<?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: ASA 5515 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5515/m-p/3325648#M989638</link>
    <description>Hi&lt;BR /&gt;&lt;BR /&gt;Can you give more details on what you're trying to achieve?&lt;BR /&gt;&lt;BR /&gt;Is it having ASA acting as CA server or looking ASA with a corporate CA?&lt;BR /&gt;&lt;BR /&gt;And then leverage vpn authentication with certificates?</description>
    <pubDate>Mon, 05 Feb 2018 22:49:41 GMT</pubDate>
    <dc:creator>Francesco Molino</dc:creator>
    <dc:date>2018-02-05T22:49:41Z</dc:date>
    <item>
      <title>ASA 5515</title>
      <link>https://community.cisco.com/t5/network-security/asa-5515/m-p/3325208#M989637</link>
      <description>&lt;P&gt;Good Day&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible&amp;nbsp;to apply an internal CA certificate to an ASA internal interface and SSL VPN feature?&lt;/P&gt;
&lt;P&gt;If so how does one go about doing so?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:17:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5515/m-p/3325208#M989637</guid>
      <dc:creator>IamDaMayor</dc:creator>
      <dc:date>2020-02-21T15:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5515</title>
      <link>https://community.cisco.com/t5/network-security/asa-5515/m-p/3325648#M989638</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Can you give more details on what you're trying to achieve?&lt;BR /&gt;&lt;BR /&gt;Is it having ASA acting as CA server or looking ASA with a corporate CA?&lt;BR /&gt;&lt;BR /&gt;And then leverage vpn authentication with certificates?</description>
      <pubDate>Mon, 05 Feb 2018 22:49:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5515/m-p/3325648#M989638</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2018-02-05T22:49:41Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5515</title>
      <link>https://community.cisco.com/t5/network-security/asa-5515/m-p/3327362#M989639</link>
      <description>&lt;P&gt;When users browses to the management / internal facing IP of the ASA (to access the ASDM) the&amp;nbsp;attached message appears.&lt;/P&gt;
&lt;P&gt;How does user apply a certificate to prevent this invalid message appearing ?&amp;nbsp;Users does not want the ASA to be a CA, but would like the ASA to have a Corporate CA cert attached to it. But there are no certificates needed for VPNs at this time&lt;/P&gt;</description>
      <pubDate>Thu, 08 Feb 2018 09:36:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5515/m-p/3327362#M989639</guid>
      <dc:creator>IamDaMayor</dc:creator>
      <dc:date>2018-02-08T09:36:57Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5515</title>
      <link>https://community.cisco.com/t5/network-security/asa-5515/m-p/3327996#M989640</link>
      <description>&lt;P&gt;OK got it.&lt;/P&gt;
&lt;P&gt;You can create a certificate for ASA. Follow that Cisco doc:&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security-vpn/public-key-infrastructure-pki/200339-Configure-ASA-SSL-Digital-Certificate-I.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security-vpn/public-key-infrastructure-pki/200339-Configure-ASA-SSL-Digital-Certificate-I.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you generate a certificate with an internal CA, users must have the chain (root and subordinate) to trust that certificate.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can also get a public certificate to not get this message for any users...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Feb 2018 02:06:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5515/m-p/3327996#M989640</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2018-02-09T02:06:37Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5515</title>
      <link>https://community.cisco.com/t5/network-security/asa-5515/m-p/3328062#M989641</link>
      <description>&lt;P&gt;User has already tried using that link but as per user it was not helpful&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;User would like to apply an internal cert to the management interface (used on the internal network).&lt;/P&gt;</description>
      <pubDate>Fri, 09 Feb 2018 07:14:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5515/m-p/3328062#M989641</guid>
      <dc:creator>IamDaMayor</dc:creator>
      <dc:date>2018-02-09T07:14:01Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5515</title>
      <link>https://community.cisco.com/t5/network-security/asa-5515/m-p/3328252#M989642</link>
      <description>&lt;P&gt;I'm sorry but I don't understand your issue here.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The link is talking about importing a certificate on ASA (no matter if that's a public or internal CA).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The goal is to :&lt;/P&gt;
&lt;P&gt;- create a trustpoint&lt;/P&gt;
&lt;P&gt;- authenticate that trustpoint by importing your Root CA&lt;/P&gt;
&lt;P&gt;- Use openssl to generate your ASA cert&lt;/P&gt;
&lt;P&gt;- import the cert into ASA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Steps are the same for internal certificate or external certificate&lt;/P&gt;</description>
      <pubDate>Fri, 09 Feb 2018 15:15:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5515/m-p/3328252#M989642</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2018-02-09T15:15:21Z</dc:date>
    </item>
  </channel>
</rss>

