<?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: Create Policy based on workstation name and AD group membership? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26743#M19522</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the idea, this seems like it would probably work for me.&amp;nbsp; I'm not on 5.x yet but I'll look into an upgrade to potentially use this solution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Apr 2013 15:48:38 GMT</pubDate>
    <dc:creator>promsos</dc:creator>
    <dc:date>2013-04-18T15:48:38Z</dc:date>
    <item>
      <title>Create Policy based on workstation name and AD group membership?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26740#M19519</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm wondering if there is a way to create a policy based on workstations in a certain AD group.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's what I'm trying to accomplish...&amp;nbsp; I want to have a security group in our Active Directory, say "Privileged Workstations" for a name.&amp;nbsp; Any workstation that is a member of the "Privileged Workstations" group will have a static IP and will need to have access to applications that are outside of our normal scope of allowed applications.&amp;nbsp; My goal is to setup a sort of self service group for our server team so if a server needs access to LogMeIn, for example, they can simply add the server to the AD group and I won't need to make any changes on my Palo Alto itself.&amp;nbsp; I do not want to write my Policy based on username as the username for the servers is not consistently identified (unless there is a way to statically create a username to ip mapping?).&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone set anything up like this before?&amp;nbsp; Maybe I'm just missing something really easy, or maybe this just can't be accomplished.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be appreciated.&amp;nbsp; Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Apr 2013 14:59:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26740#M19519</guid>
      <dc:creator>promsos</dc:creator>
      <dc:date>2013-04-17T14:59:54Z</dc:date>
    </item>
    <item>
      <title>Re: Create Policy based on workstation name and AD group membership?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26741#M19520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe you could create an "dynamic address object" and use it in the firewall rule. Then craft a script that reads the AD group and writes to the dynamic address object via XML API.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A __default_attr="4121" __jive_macro_name="document" class="jive_macro jive_macro_document" href="https://live.paloaltonetworks.com/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Apr 2013 20:29:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26741#M19520</guid>
      <dc:creator>Anon1</dc:creator>
      <dc:date>2013-04-17T20:29:45Z</dc:date>
    </item>
    <item>
      <title>Re: Create Policy based on workstation name and AD group membership?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26742#M19521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when a user wants to get connect to for example LogMeIn then he is known on the AD-Server.&amp;nbsp; The security group in the policy can be used because the group is also known on the AD-Server (the user have to be a member of this group)&lt;/P&gt;&lt;P&gt;The PAN-Agent is looking into the log of AD-Server ( it is not necessary to use an AD-Server) and sends this data to the Palo Alto. so the PA knows the IP and no user or ip-address has to be used.&amp;nbsp; may the service or the app is changing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Apr 2013 15:36:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26742#M19521</guid>
      <dc:creator>kdd</dc:creator>
      <dc:date>2013-04-18T15:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: Create Policy based on workstation name and AD group membership?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26743#M19522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the idea, this seems like it would probably work for me.&amp;nbsp; I'm not on 5.x yet but I'll look into an upgrade to potentially use this solution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Apr 2013 15:48:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26743#M19522</guid>
      <dc:creator>promsos</dc:creator>
      <dc:date>2013-04-18T15:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: Create Policy based on workstation name and AD group membership?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26744#M19523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Klaus - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe my example of using LogMeIn wasn't the best example to use in this situation because that may require a user to go out and manually initiate a connection.&amp;nbsp; What we'll really be doing is allowing a vendor to remotely connect to certain PC's in our company via TeamViewer or a similar app.&amp;nbsp; It's possible that these machines won't actually be logged into by a user for months (they just sit there pulling and pushing data) and even when service is needed a user probably won't be logging into the machine before support tries to connect remotely.&amp;nbsp; Because user's won't login often (if at all) any solution using a username won't work for us since the username will most liekly .&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe I misunderstood the solution you're proposing, if so just let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Apr 2013 16:09:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/create-policy-based-on-workstation-name-and-ad-group-membership/m-p/26744#M19523</guid>
      <dc:creator>promsos</dc:creator>
      <dc:date>2013-04-18T16:09:14Z</dc:date>
    </item>
  </channel>
</rss>

