<?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 Cisco ASA as trusted authority for internal websites in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190591#M1076249</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am managing a CISCO Asa for a client. WAN Connection ends up in a ISR Router who is doing the NAT and after the ISR is the ASA.&lt;/P&gt;&lt;P&gt;On the inside there are few websites held by a Windows Server 2012-2016 AD infrastructure.&lt;/P&gt;&lt;P&gt;For internal hosts, client uses DC self-signed certificate.&lt;/P&gt;&lt;P&gt;For AnyConnect users to connect to the ASA we have 3rd party certificate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I am looking after is a solution for the external hosts ( coming via AnyConnect vpn) to see the internal websites as secure - the green lock as the client sees it.&lt;/P&gt;&lt;P&gt;Client does not want to purchase individual certs for websites , also the external hosts cannot be added to the domain.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Thanks&lt;/P&gt;&lt;P&gt;Andrei&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Nov 2020 10:12:03 GMT</pubDate>
    <dc:creator>andreitoma22</dc:creator>
    <dc:date>2020-11-30T10:12:03Z</dc:date>
    <item>
      <title>Cisco ASA as trusted authority for internal websites</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190591#M1076249</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am managing a CISCO Asa for a client. WAN Connection ends up in a ISR Router who is doing the NAT and after the ISR is the ASA.&lt;/P&gt;&lt;P&gt;On the inside there are few websites held by a Windows Server 2012-2016 AD infrastructure.&lt;/P&gt;&lt;P&gt;For internal hosts, client uses DC self-signed certificate.&lt;/P&gt;&lt;P&gt;For AnyConnect users to connect to the ASA we have 3rd party certificate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I am looking after is a solution for the external hosts ( coming via AnyConnect vpn) to see the internal websites as secure - the green lock as the client sees it.&lt;/P&gt;&lt;P&gt;Client does not want to purchase individual certs for websites , also the external hosts cannot be added to the domain.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Thanks&lt;/P&gt;&lt;P&gt;Andrei&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Nov 2020 10:12:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190591#M1076249</guid>
      <dc:creator>andreitoma22</dc:creator>
      <dc:date>2020-11-30T10:12:03Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA as trusted authority for internal websites</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190609#M1076252</link>
      <description>&lt;P&gt;There is no other way than providing a valid certificate to the client. If the external clients also belong to the company, than just provide the clients the root-certificate that you used to provide certificates to the internal servers. IMO, a dirty solution which I would not like to implement, but technically it will work.&lt;/P&gt;
&lt;P&gt;The better solution is to work with official certificates here. For that, you can either install the certificates on the local servers, or implement a "gateway" for this:&lt;/P&gt;
&lt;P&gt;Place a linux server into your DMZ and configure it to act as a reverse proxy. The open source webserver NGINX can do that pretty well. This reverse-proxy is configured with the public certificate, and can even automate the enrollment for free LetsEncrypt certificates. The external users acess the reverse-proxy which builds a new connection to the internal server to present the content.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Nov 2020 10:32:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190609#M1076252</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2020-11-30T10:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA as trusted authority for internal websites</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190687#M1076262</link>
      <description>&lt;P&gt;Karsten,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp; a lot for your reply, really helpful, indeed I like the reverse-proxy solution better, but just to make sure I got the clear picture - is there a way to feed the self-certificate used in the servers to the external clients - via AnyConnect maybe, can ASA push this when negotiating connection - or which delivery method would suit best ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks Andrei&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Nov 2020 12:19:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190687#M1076262</guid>
      <dc:creator>andreitoma22</dc:creator>
      <dc:date>2020-11-30T12:19:13Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA as trusted authority for internal websites</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190693#M1076264</link>
      <description>&lt;P&gt;There is no automatic import for the VPN users. It the remote PCs are part of your Active-Directory domain, you can push the certificate with a GPO. Same if you have any kind of management system for the PCs. This can do the job too.&lt;/P&gt;
&lt;P&gt;If you don't have any of this, then the users have to import the certificate manually.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Nov 2020 12:32:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190693#M1076264</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2020-11-30T12:32:46Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA as trusted authority for internal websites</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190697#M1076265</link>
      <description>&lt;P&gt;Thanks again, I will look into the r&lt;SPAN&gt;everse-proxy solution.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Andrei&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Nov 2020 12:40:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190697#M1076265</guid>
      <dc:creator>andreitoma22</dc:creator>
      <dc:date>2020-11-30T12:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA as trusted authority for internal websites</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190708#M1076267</link>
      <description>&lt;P&gt;Another option is one of the free load-balancers. KEMP has a free version of their LoadMaster Software. Of course it is restricted in throughput, but could perhaps be the right solution:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.kemptechnologies.com/hc/en-us/articles/204427785" target="_blank"&gt;https://support.kemptechnologies.com/hc/en-us/articles/204427785&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Nov 2020 12:58:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-as-trusted-authority-for-internal-websites/m-p/4190708#M1076267</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2020-11-30T12:58:57Z</dc:date>
    </item>
  </channel>
</rss>

