<?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 First create some objects to in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/accessing-dmz-from-one-ip/m-p/2866459#M172430</link>
    <description>&lt;P&gt;First create some objects to make a nice config.&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;object network&amp;nbsp;application-server-name&lt;BR /&gt;&amp;nbsp;host x.x.x.x&lt;BR /&gt;&lt;SPAN&gt;object network&amp;nbsp;db&lt;/SPAN&gt;&lt;SPAN&gt;-server-name&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;host x.x.x.x&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;Then create a rule to allow traffic from DMZ to inside.&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;access-list dmz_access_in extended permit tcp object&amp;nbsp;&lt;SPAN&gt;application-server-name&lt;/SPAN&gt; object &lt;SPAN&gt;db&lt;/SPAN&gt;&lt;SPAN&gt;-server-name&lt;/SPAN&gt; eq &amp;lt;tcp port&amp;gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;access-group dmz_access_in in interface&amp;nbsp;dmz&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;Then create an object NAT rule for the application server. &amp;nbsp;In this case, I'm going to assume you are using the firewall's IP address itself.&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;object network&amp;nbsp;application-server-name&lt;BR /&gt;  &amp;nbsp;nat (dmz,outside) static&amp;nbsp;interface service tcp 443 443&lt;/PRE&gt;
&lt;P&gt;And lastly, you need a rule on the outside interface to allow the traffic in.&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;access-list outside_access_in extended permit tcp any object application&lt;SPAN&gt;-server-name&lt;/SPAN&gt; eq 443&lt;BR /&gt;&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;access-group outside_access_in in interface&amp;nbsp;outside&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 18 Feb 2016 08:59:32 GMT</pubDate>
    <dc:creator>Philip D'Ath</dc:creator>
    <dc:date>2016-02-18T08:59:32Z</dc:date>
    <item>
      <title>Accessing DMZ from one IP</title>
      <link>https://community.cisco.com/t5/network-security/accessing-dmz-from-one-ip/m-p/2866458#M172429</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;I would like to kindly ask you for help with configuration of Cisco ASA 5505. Need to say that I am beginner in ASA networking &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I have standard network model configured on ASA. DMZ,OUTSIDE,INSIDE. In DMZ I have application server which needs to communicate with DB server in inside. I know that best practise is to disable all communication from DMZ to inside but I can't do it in different way now. So my question has two parts.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1) how to allow communication between DMZ and inside on one specific port (MSSQL)?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;2) as I will create some potencional threat because of opening communication between DMZ and inside, I would like to allow communication from outside to DMZ on 443 (also certificate will be need to access application server) and also allow this communication only from one specific outside IP address. Only one organization with public IP will need to connect to our appsrv.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Many thanks for your answers&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:19:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accessing-dmz-from-one-ip/m-p/2866458#M172429</guid>
      <dc:creator>michalberanek1</dc:creator>
      <dc:date>2019-03-12T07:19:46Z</dc:date>
    </item>
    <item>
      <title>First create some objects to</title>
      <link>https://community.cisco.com/t5/network-security/accessing-dmz-from-one-ip/m-p/2866459#M172430</link>
      <description>&lt;P&gt;First create some objects to make a nice config.&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;object network&amp;nbsp;application-server-name&lt;BR /&gt;&amp;nbsp;host x.x.x.x&lt;BR /&gt;&lt;SPAN&gt;object network&amp;nbsp;db&lt;/SPAN&gt;&lt;SPAN&gt;-server-name&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;host x.x.x.x&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;Then create a rule to allow traffic from DMZ to inside.&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;access-list dmz_access_in extended permit tcp object&amp;nbsp;&lt;SPAN&gt;application-server-name&lt;/SPAN&gt; object &lt;SPAN&gt;db&lt;/SPAN&gt;&lt;SPAN&gt;-server-name&lt;/SPAN&gt; eq &amp;lt;tcp port&amp;gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;access-group dmz_access_in in interface&amp;nbsp;dmz&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;Then create an object NAT rule for the application server. &amp;nbsp;In this case, I'm going to assume you are using the firewall's IP address itself.&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;object network&amp;nbsp;application-server-name&lt;BR /&gt;  &amp;nbsp;nat (dmz,outside) static&amp;nbsp;interface service tcp 443 443&lt;/PRE&gt;
&lt;P&gt;And lastly, you need a rule on the outside interface to allow the traffic in.&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;access-list outside_access_in extended permit tcp any object application&lt;SPAN&gt;-server-name&lt;/SPAN&gt; eq 443&lt;BR /&gt;&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;PRE class="prettyprint"&gt;&lt;SPAN&gt;access-group outside_access_in in interface&amp;nbsp;outside&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2016 08:59:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accessing-dmz-from-one-ip/m-p/2866459#M172430</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-02-18T08:59:32Z</dc:date>
    </item>
  </channel>
</rss>

