<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Microsoft-Dynamic-Access-Control on The IT Hollow</title>
    <link>https://theithollow.com/categories/microsoft-dynamic-access-control/</link>
    <description>Recent content in Microsoft-Dynamic-Access-Control on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 28 Apr 2014 13:05:45 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/categories/microsoft-dynamic-access-control/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Microsoft Dynamic Access Control (Part 1)</title>
      <link>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-1/</link>
      <pubDate>Mon, 28 Apr 2014 13:05:45 +0000</pubDate>
      <guid>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-1/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;Locked&#34; loading=&#34;lazy&#34; src=&#34;https://assets.theithollow.com/wp-content/uploads/2014/01/Locked-300x242.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Microsoft Dynamic Access Control is a new way to deploy access rules to your file shares.  For many moons now, System Administrators have had a tedious task of managing tens, hundreds, or thousands of security groups to control how files are accessed.&lt;/p&gt;
&lt;p&gt;Groups of users have always needed to maintain different sets of security rules to prevent people from accessing confidential files.  Human Resources obviously doesn&amp;rsquo;t want people outside their department to have access to personnel files, separate office locations may not want to share data with other offices in the same domain, and countries or cities might have different restrictions about sharing files with each other.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Dynamic Access Control (Part 2 - Claims)</title>
      <link>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-2-claims/</link>
      <pubDate>Mon, 28 Apr 2014 13:04:52 +0000</pubDate>
      <guid>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-2-claims/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;http://wp.me/p32uaN-NX&#34;&gt;part 1 of the series&lt;/a&gt; we covered some generalities about Microsoft Dynamic Access Control and a few steps needed to prepare the domain and file servers.  Now let&amp;rsquo;s look at creating claims.&lt;/p&gt;
&lt;p&gt;A claim is a user, device or resource property.  A user in Active Directory will have properties such as Location, Department, manager, etc.  Each of these properties is a claim but for any actions to be utilized by Direct Access, they have to be defined.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Dynamic Access Control (Part 3 – Resource Properties)</title>
      <link>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-3-resource-properties/</link>
      <pubDate>Mon, 28 Apr 2014 13:03:00 +0000</pubDate>
      <guid>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-3-resource-properties/</guid>
      <description>&lt;p&gt;So far we&amp;rsquo;ve covered:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;http://wp.me/p32uaN-NX&#34;&gt;Initial Setup of Dynamic Access Control&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;http://wp.me/p32uaN-O2&#34;&gt;Claims&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In this post we&amp;rsquo;ll look at Resource Properties.&lt;/p&gt;
&lt;h1 id=&#34;resource-properties&#34;&gt;Resource Properties&lt;/h1&gt;
&lt;p&gt;A resource property is a claim that describes the characteristics of an object in the file system.  A claim is a descriptor of a user or a device whereas a resource property is a characteristic of a file or folder.&lt;/p&gt;
&lt;p&gt;As an example, we have a folder with HIPPA related information in it.  A description can be added to this folder to indicate that it has Protected Health Information (PHI) contained in that folder.  This PHI description is a resource property.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Dynamic Access Control (Part 4 – Rules and Policies)</title>
      <link>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-4-rules-policies/</link>
      <pubDate>Mon, 28 Apr 2014 13:01:47 +0000</pubDate>
      <guid>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-4-rules-policies/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve discussed &lt;a href=&#34;http://wp.me/p32uaN-NX&#34;&gt;Initial configuration steps&lt;/a&gt;, &lt;a href=&#34;http://wp.me/p32uaN-O2&#34;&gt;Claims&lt;/a&gt;, and &lt;a href=&#34;http://wp.me/p32uaN-Oi&#34;&gt;Resource Properties&lt;/a&gt; and we&amp;rsquo;re starting to see the power of Microsoft&amp;rsquo;s Dynamic Access Control, but we need a better way to manage these and that&amp;rsquo;s why we&amp;rsquo;ve come to &amp;ldquo;Rules and Policies&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;A Central Access Rule can be used to take claims such as users in a department and match them up with permissions on a filefolder with specific resource properties.  This is where the real power comes into play because now we don&amp;rsquo;t have to go through and map these for each individual file.  We&amp;rsquo;re setting a general policy for the entire organization all at once.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Dynamic Access Control (Part 5 - Auto Classification)</title>
      <link>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-5-auto-classification/</link>
      <pubDate>Mon, 28 Apr 2014 13:00:33 +0000</pubDate>
      <guid>https://theithollow.com/2014/04/28/microsoft-dynamic-access-control-part-5-auto-classification/</guid>
      <description>&lt;p&gt;In the first four parts of the Dynamic Access Control Series we covered &lt;a href=&#34;http://wp.me/p32uaN-NX&#34;&gt;Initial Configurations&lt;/a&gt;, &lt;a href=&#34;http://wp.me/p32uaN-O2&#34;&gt;Claims&lt;/a&gt;, &lt;a href=&#34;http://wp.me/p32uaN-Oi&#34;&gt;Resource Properties&lt;/a&gt; and &lt;a href=&#34;http://wp.me/p32uaN-Ox&#34;&gt;Rules Policies&lt;/a&gt;.  These are working great in our environment but we still have to go through and manage the classification tags.  Wouldn&amp;rsquo;t it be easier to have some files automatically tagged with a certain resource classification?&lt;/p&gt;
&lt;p&gt;Enter File Server Resource Manager to the rescue!&lt;/p&gt;
&lt;h1 id=&#34;classification-rules&#34;&gt;Classification Rules&lt;/h1&gt;
&lt;p&gt;From within File Server Resource Manager (FSRM) go to Classification Rules and choose to &amp;ldquo;Create Classification Rule&amp;hellip;&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
