WEBVTT

0:00:02.620000 --> 0:00:06.620000
 Hi, I want to take just a moment before
 this video starts to let you know

0:00:06.620000 --> 0:00:12.060000
 that this video, which covers centralized
 and security policy management,

0:00:12.060000 --> 0:00:16.340000
 is really a combination of two things
 that are covered in many other videos,

0:00:16.340000 --> 0:00:18.980000
 security center and policy.

0:00:18.980000 --> 0:00:22.480000
 And if you are familiar with both security
 center and policy and kind

0:00:22.480000 --> 0:00:27.460000
 of see how they go together to let you
 manage your overall security footprint,

0:00:27.460000 --> 0:00:30.340000
 then you might be able to
 skip through this video.

0:00:30.340000 --> 0:00:34.280000
 Otherwise, or even if you just want to
 make sure, I will try to make this

0:00:34.280000 --> 0:00:35.600000
 as efficient as possible.

0:00:35.600000 --> 0:00:38.940000
 Always do. What we're going to talk
 about is first of all, we want to

0:00:38.940000 --> 0:00:41.740000
 have central security
 policy, right?

0:00:41.740000 --> 0:00:45.140000
 You may have thousands
 of resources.

0:00:45.140000 --> 0:00:48.360000
 How do you make sure that you've
 got a consistent policy?

0:00:48.360000 --> 0:00:50.900000
 We'll talk about customizing
 policy.

0:00:50.900000 --> 0:00:53.940000
 We'll also take a look at
 regulatory compliance.

0:00:53.940000 --> 0:00:58.120000
 And then I am going to demonstrate
 security policy.

0:00:58.120000 --> 0:01:00.360000
 Let's go ahead and jump right in.

0:01:00.360000 --> 0:01:06.200000
 Okay, first of all, there is a tool, of
 course, in Azure for really centralizing

0:01:06.200000 --> 0:01:08.880000
 all of your security and
 that is security center.

0:01:08.880000 --> 0:01:14.200000
 And really, it simply
 relies on policies.

0:01:14.200000 --> 0:01:18.680000
 Okay, so you apply policies through
 security center and you can apply

0:01:18.680000 --> 0:01:21.660000
 them at subscription level.

0:01:21.660000 --> 0:01:24.560000
 If possible, you kind of always want
 to go up as high in the stack as

0:01:24.560000 --> 0:01:29.740000
 you can. Always a good idea to apply
 your policy at the management group

0:01:29.740000 --> 0:01:35.260000
 level. Same idea as not having to manage
 a, you know, a number of individual

0:01:35.260000 --> 0:01:40.720000
 resources. I can set my policy
 at a management group.

0:01:40.720000 --> 0:01:43.700000
 And then I know it's going to apply
 to all the subscriptions underneath

0:01:43.700000 --> 0:01:45.500000
 of that management group.

0:01:45.500000 --> 0:01:52.360000
 Now, there is a standard built
 in policy that you can modify.

0:01:52.360000 --> 0:01:57.140000
 It's a really, it's actually not so much
 a policy as it is an initiative.

0:01:57.140000 --> 0:01:59.940000
 Actually, it absolutely
 is an initiative.

0:01:59.940000 --> 0:02:04.480000
 And in fact, that initiative includes
 over 90 specific policies.

0:02:04.480000 --> 0:02:09.140000
 And you can configure the basics
 of that through security center.

0:02:09.140000 --> 0:02:13.340000
 So you have some choices, you can apply
 the standard policy, but also

0:02:13.340000 --> 0:02:18.000000
 through some parameters, you have
 significant control over that.

0:02:18.000000 --> 0:02:23.420000
 If that is not enough, then just like
 any other policy scenario, you can

0:02:23.420000 --> 0:02:28.780000
 create your own custom policies or build
 your own custom initiatives that

0:02:28.780000 --> 0:02:29.960000
 may include custom policies.

0:02:29.960000 --> 0:02:35.740000
 It may also include some of the over 400
 built in policies that are available

0:02:35.740000 --> 0:02:38.400000
 out of the box with Azure.

0:02:38.400000 --> 0:02:42.480000
 Right, once you create the initiative,
 then just like with the standard,

0:02:42.480000 --> 0:02:46.040000
 you're going to apply that initiative
 to a management group or subscription.

0:02:46.040000 --> 0:02:51.100000
 And so really, the story here is the
 same story that's told really in

0:02:51.100000 --> 0:02:53.920000
 different places throughout
 our Azure content.

0:02:53.920000 --> 0:02:56.320000
 And that is that you want
 to use policy, right?

0:02:56.320000 --> 0:03:02.720000
 Policy lets you, you know, start and
 run and monitor and be able to do

0:03:02.720000 --> 0:03:07.340000
 that passively. Although, of course,
 you want to make sure you set up

0:03:07.340000 --> 0:03:11.380000
 alerts and you want to make sure that
 you are actually going into security

0:03:11.380000 --> 0:03:16.360000
 center and keeping track of what this
 policy is pulling up for you.

0:03:16.360000 --> 0:03:21.760000
 Fortunately for you, I am completely sloppy
 in my demonstration subscription.

0:03:21.760000 --> 0:03:25.600000
 So you'll see lots of recommendations
 that are coming from these security

0:03:25.600000 --> 0:03:27.940000
 policies in the demonstration.

0:03:27.940000 --> 0:03:38.020000
 Now, another thing that you now
 integrated into security center.

0:03:38.020000 --> 0:03:45.080000
 There are a number of built in industry
 standards that pretty much once

0:03:45.080000 --> 0:03:48.840000
 you're running security center, you're
 going to get these standards and

0:03:48.840000 --> 0:03:52.720000
 you can go into individual standards
 and see how compliant you are.

0:03:52.720000 --> 0:03:56.960000
 And that actually surfaces at the dashboard
 level, the top dashboard level

0:03:56.960000 --> 0:03:58.760000
 within security center.

0:03:58.760000 --> 0:04:07.100000
 There are a number of additional regulatory
 compliance options that you

0:04:07.100000 --> 0:04:14.840000
 can add. So if, for example, you are
 subject to missed sp 800-53 R4, you

0:04:14.840000 --> 0:04:19.420000
 can add that in and it's automatically
 going to look for the Azure related

0:04:19.420000 --> 0:04:22.960000
 requirements. Now, one thing to keep
 in mind, this is looking at what

0:04:22.960000 --> 0:04:33.700000
 Azure is doing. It's not going
 to do everything for you.

0:04:33.700000 --> 0:04:37.200000
 It's taking care of the Azure part and
 that is a significant advantage,

0:04:37.200000 --> 0:04:42.640000
 but you still have to make sure that
 you're keeping track of your part

0:04:42.640000 --> 0:04:47.240000
 of this. And here's an example of what
 you would see with the different

0:04:47.240000 --> 0:04:52.120000
 compliance. And you'll see that I've
 actually got pretty good compliance

0:04:52.120000 --> 0:04:58.020000
 with Azure CIS. All of these, of course,
 are well documented and less

0:04:58.020000 --> 0:05:00.980000
 compliance with SOC TSP.

0:05:00.980000 --> 0:05:04.600000
 All right. Now, what I'm going to do
 is I'm just going to go ahead and

0:05:04.600000 --> 0:05:06.920000
 demonstrate security policies.

0:05:06.920000 --> 0:05:10.300000
 So I'm going to take a look at security
 center, and I'm going to go right

0:05:10.300000 --> 0:05:11.900000
 into policies for security center.


0:05:11.900000 --> 0:05:15.360000
 And we're going to take a look at what's
 there, show you how you can configure

0:05:15.360000 --> 0:05:20.800000
 your base policy and then take a look
 not only a policy, but also regulatory

0:05:20.800000 --> 0:05:25.060000
 compliance. And look at the output of
 both of those from the standpoint,

0:05:25.060000 --> 0:05:28.120000
 starting at the security
 center dashboard.

0:05:28.120000 --> 0:05:31.620000
 So let's go ahead and
 let's jump into this.

0:05:31.620000 --> 0:05:34.840000
 All right. Here is
 security center.

0:05:34.840000 --> 0:05:40.320000
 And right off the bat, I see I've got security
 policy and regulatory compliance.

0:05:40.320000 --> 0:05:41.920000
 I'm going to go to
 security policy.

0:05:41.920000 --> 0:05:45.200000
 So here's my policy management.

0:05:45.200000 --> 0:05:47.140000
 And I've got it by
 management group.

0:05:47.140000 --> 0:05:51.360000
 And I can also go into individual
 subscriptions.

0:05:51.360000 --> 0:05:54.820000
 And despite me telling you that you
 should go up in the higher level,

0:05:54.820000 --> 0:06:01.220000
 just demonstration purposes, I am going
 to go to the policy for a specific

0:06:01.220000 --> 0:06:04.700000
 subscription. Okay.

0:06:04.700000 --> 0:06:08.480000
 Now I've got policy and I've got
 compliance all right here.

0:06:08.480000 --> 0:06:11.640000
 I'm going to view
 effective policy.

0:06:11.640000 --> 0:06:14.120000
 And this is showing me
 what my policies are.

0:06:14.120000 --> 0:06:16.960000
 So here is my compute and apps.

0:06:16.960000 --> 0:06:21.000000
 These are all of the policies that
 apply to compute and apps.

0:06:21.000000 --> 0:06:22.260000
 Here's my network.

0:06:22.260000 --> 0:06:25.700000
 Notice only seven out of eight
 of those are enabled.

0:06:25.700000 --> 0:06:32.940000
 Data policies. And I can see what's
 enabled identity policies.

0:06:32.940000 --> 0:06:33.620000
 And there we go.

0:06:33.620000 --> 0:06:35.700000
 So identity data network.

0:06:35.700000 --> 0:06:39.040000
 And also compute.

0:06:39.040000 --> 0:06:42.500000
 Now it's a little bit, I don't like
 the link and maybe by the time you

0:06:42.500000 --> 0:06:44.220000
 run this and play around with it.

0:06:44.220000 --> 0:06:48.260000
 Maybe they'll change this because
 it's already enabled.

0:06:48.260000 --> 0:06:52.680000
 But I have to click this if I want
 to edit the policy, which again is

0:06:52.680000 --> 0:06:54.360000
 really an initiative.

0:06:54.360000 --> 0:06:59.500000
 If I click on that link, it's going
 to go into my initiative editor.

0:06:59.500000 --> 0:07:04.520000
 And what that's going to allow me to do
 pretty much if I go here to parameters.

0:07:04.520000 --> 0:07:07.480000
 Okay, these are all of these
 setable parameters.

0:07:07.480000 --> 0:07:12.860000
 So, for example, you know, if I wanted
 to so manage certificate validity

0:07:12.860000 --> 0:07:18.540000
 period, I could audit that.

0:07:18.540000 --> 0:07:22.600000
 So if I've got managed certificates,
 and you can see quite a number of

0:07:22.600000 --> 0:07:25.220000
 audit if not exists.

0:07:25.220000 --> 0:07:28.440000
 All right, it's not all just whether
 or not you audit some are settings

0:07:28.440000 --> 0:07:31.100000
 like data lakes analytics.

0:07:31.100000 --> 0:07:34.180000
 How long do you want to
 require that to be kept?

0:07:34.180000 --> 0:07:38.860000
 That's 365. And so you see
 just a number of options.

0:07:38.860000 --> 0:07:41.260000
 I'm going to cancel out of this.

0:07:41.260000 --> 0:07:47.980000
 Because again, it's really just standard
 policy slash initiative configuration.

0:07:47.980000 --> 0:07:54.100000
 One of the things a little bit more
 interesting if I go back here is my

0:07:54.100000 --> 0:07:57.400000
 industry and regulatory standards.


0:07:57.400000 --> 0:08:00.520000
 Oh, and by the way, I can add my own
 custom initiatives right there.

0:08:00.520000 --> 0:08:04.600000
 You can also do that through the
 policy configuration in Azure.

0:08:04.600000 --> 0:08:09.520000
 Okay, so here are the available
 regulatory compliance standards.

0:08:09.520000 --> 0:08:13.600000
 So let's say in addition what I already
 have, I want to add, I was commonly

0:08:13.600000 --> 0:08:16.280000
 referred to as HIPAA.

0:08:16.280000 --> 0:08:18.960000
 Okay, and we say, okay,
 here's basic.

0:08:18.960000 --> 0:08:22.620000
 Going there, and I would
 set all this up.

0:08:22.620000 --> 0:08:25.860000
 I'm not going to add this because I
 don't want to take time to set up

0:08:25.860000 --> 0:08:31.080000
 all of these required settings
 and do something haphazard.

0:08:31.080000 --> 0:08:33.860000
 But that is how easy it is.

0:08:33.860000 --> 0:08:37.040000
 And of course, if you're setting up
 HIPAA, you probably should have a

0:08:37.040000 --> 0:08:40.280000
 good idea of what you
 need to set up.

0:08:40.280000 --> 0:08:43.860000
 Okay, now, how do these show up?

0:08:43.860000 --> 0:08:50.440000
 If I go to regulatory compliance, I
 can see that I've got my different

0:08:50.440000 --> 0:08:58.140000
 regulatory compliance and if I click
 in here, it'll make me go in here

0:08:58.140000 --> 0:08:59.640000
 somewhere. Oh, there we go.

0:08:59.640000 --> 0:09:02.400000
 It's down here. That's why, because
 it's all on one page.

0:09:02.400000 --> 0:09:07.160000
 All right, so here are my
 regulatory compliance.

0:09:07.160000 --> 0:09:12.180000
 And I can see Azure CIS, I've got
 lots of green, which is great.

0:09:12.180000 --> 0:09:17.060000
 Right now, if I go into identity and
 access management, it's always MFA.

0:09:17.060000 --> 0:09:30.660000
 All right, because my network director
 has to have access, all the time.

0:09:30.660000 --> 0:09:33.720000
 All right, and then virtual machine,
 I can see, okay, what's compliance

0:09:33.720000 --> 0:09:36.160000
 there? I need data encryption.

0:09:36.160000 --> 0:09:37.900000
 Now, you'll see a lot
 of overlap, right?

0:09:37.900000 --> 0:09:45.300000
 So if I go PCI, all sorts of problems
 there, should see somewhere down

0:09:45.300000 --> 0:09:51.260000
 here. Oh, PCI doesn't have it,
 but lots of different piece.

0:09:51.260000 --> 0:10:00.080000
 One of these also has, there it is,
 I believe, user access management,

0:10:00.080000 --> 0:10:05.940000
 somewhere in here,
 there you go, MFA.

0:10:05.940000 --> 0:10:11.800000
 So I had to drive down a little bit
 and find it, but drill down a little

0:10:11.800000 --> 0:10:14.300000
 bit. But in any case,
 that's pretty cool.

0:10:14.300000 --> 0:10:21.540000
 It's, you know, buy
 your application.

0:10:21.540000 --> 0:10:25.060000
 I can also manage the compliance policies,
 which pulls me right back to

0:10:25.060000 --> 0:10:29.140000
 here. All right, and so the end of the
 day, what does all that give me?

0:10:29.140000 --> 0:10:34.080000
 Well, it gives me this, right?

0:10:34.080000 --> 0:10:37.780000
 And that's going to, of course, show
 up, for example, in my compute and

0:10:37.780000 --> 0:10:41.380000
 apps, etc. But I think particularly
 for regulatory compliance, you know,

0:10:41.380000 --> 0:10:43.900000
 if you are subject to regulations, it's
 just real nice to be able to come

0:10:43.900000 --> 0:10:47.380000
 in here, say, okay, how
 am I doing on SOC TSP?

0:10:47.380000 --> 0:10:49.140000
 Where do I need to fix things?

0:10:49.140000 --> 0:10:51.560000
 And you want to be all
 green, of course.

0:10:51.560000 --> 0:10:52.800000
 All right, but there you go.

0:10:52.800000 --> 0:10:58.460000
 That is how you can use Security Center
 and policy slash initiatives to

0:10:58.460000 --> 0:11:03.140000
 centralize and monitor
 your security policies.

