WEBVTT 00:00:01.640 --> 00:00:05.690 I always encourage a three‑step process as a path to 00:00:05.690 --> 00:00:09.260 preparing for any certification in the classroom. 00:00:09.840 --> 00:00:14.920 When you study, be sure to develop an understanding of and an ordering of, 00:00:14.920 --> 00:00:18.600 first, establishing definitions, second, 00:00:18.690 --> 00:00:21.920 the application of those definitions, and finally, 00:00:21.920 --> 00:00:25.050 third, the integration of all things. 00:00:25.440 --> 00:00:29.930 Making application of an exam item topic means that we know when, 00:00:29.930 --> 00:00:34.310 how, where, why, and even who uses that item. 00:00:34.310 --> 00:00:39.310 Integrating an exam item topic means that we can now blend topics and 00:00:39.310 --> 00:00:43.060 see how they fit into one another like puzzle pieces. 00:00:43.440 --> 00:00:47.630 You should be able to take an element from the first domain and see 00:00:47.630 --> 00:00:50.400 how it works with an element from the last domain. 00:00:50.590 --> 00:00:51.310 First, 00:00:51.320 --> 00:00:54.680 let's consider what's meant by establishing definitions 00:00:54.690 --> 00:00:58.000 and from where our definitions derived. 00:00:58.000 --> 00:01:03.460 Definition lays down the foundation upon which everything else is based. 00:01:03.760 --> 00:01:07.260 The definition for the CCSP, like many cyber certs, 00:01:07.270 --> 00:01:11.430 are derived from the major cybersecurity standards that 00:01:11.430 --> 00:01:14.350 are known and accepted internationally. 00:01:14.940 --> 00:01:17.020 Think ISO and NIST. 00:01:17.440 --> 00:01:21.740 So it is not helpful from a position of focus and positivity to speak 00:01:21.740 --> 00:01:25.560 about the taxonomy in the CCSP in a mocking manner, 00:01:25.560 --> 00:01:28.260 like, oh, that's the CCSP term. 00:01:28.740 --> 00:01:33.260 The terms used for the CCSP are derived from ISO and NIST. 00:01:33.740 --> 00:01:37.660 We often incorporate the standard within our organization, 00:01:37.710 --> 00:01:42.130 implementing them to fit our operating environment; therefore, 00:01:42.130 --> 00:01:46.310 we end up calling it something very different from the standard and may 00:01:46.310 --> 00:01:48.890 call it something that no longer resembles the standard. 00:01:49.640 --> 00:01:52.910 We may begin to fight with the description that we see from 00:01:52.920 --> 00:01:56.260 ISC2 or some other certification organization. 00:01:56.640 --> 00:01:59.870 I've seen this play out live in the classroom where someone will 00:01:59.870 --> 00:02:02.460 swear this is not what something is called, 00:02:02.460 --> 00:02:07.500 and then you show them in the ISO or the NIST document that it is. 00:02:07.500 --> 00:02:10.460 Suppose you are outside of the United States. 00:02:10.940 --> 00:02:11.820 In that case, 00:02:11.820 --> 00:02:15.710 you may have an allergy to the NIST documentation since its origins 00:02:15.710 --> 00:02:20.030 are in the US and the primary purpose of it is to ready the protection 00:02:20.030 --> 00:02:22.250 of federal or government systems there. 00:02:23.440 --> 00:02:26.540 The matter of fact is that the NIST standard is 00:02:26.540 --> 00:02:29.560 consumed from and contributed to globally. 00:02:30.140 --> 00:02:35.860 If you use ENISA, it calls out a basis of NIST within it. 00:02:36.540 --> 00:02:40.970 The advanced encryption standard is an example of a NIST‑sponsored global 00:02:40.970 --> 00:02:44.960 collaboration based upon two Belgian cryptologist's algorithm. 00:02:45.340 --> 00:02:49.410 An example of a definition you would want to be familiar with is 00:02:49.410 --> 00:02:53.160 found in the five characteristics of cloud computing described in 00:02:53.160 --> 00:02:57.920 NIST Special Publication 800‑145, broad network access, 00:02:57.920 --> 00:03:01.700 rapid elasticity, resource pooling, on‑demand, 00:03:01.710 --> 00:03:03.560 and measured services. 00:03:03.870 --> 00:03:08.440 These five characteristics I like to make into an acronym known as BRROM, 00:03:08.440 --> 00:03:09.960 B‑R‑R‑O‑M. 00:03:10.440 --> 00:03:14.980 If you use the latter definition of ISO 17788, 00:03:15.070 --> 00:03:17.670 then you would add another M for multitenancy. 00:03:17.670 --> 00:03:23.030 But let's focus on one element in BRROM, namely measured. 00:03:23.030 --> 00:03:23.570 Here, 00:03:23.570 --> 00:03:27.430 the provider delivers instrumentation so that an organization 00:03:27.440 --> 00:03:30.080 only pays for the services they utilize. 00:03:30.080 --> 00:03:34.380 Measured allows a nontechnology‑based company to move from being a 00:03:34.380 --> 00:03:39.280 prominent owner and manager of sizable physical technology platforms and 00:03:39.280 --> 00:03:45.260 the capitalization cost of such and move over to a model that is focused on 00:03:45.270 --> 00:03:49.890 paying for the benefits of the platform rather than the ownership and cost 00:03:49.900 --> 00:03:51.650 of what produces the benefits. 00:03:52.440 --> 00:03:55.780 Now that we have the definition and characteristics of measured, 00:03:55.950 --> 00:03:57.860 let's apply the definition. 00:03:58.240 --> 00:04:02.660 We want to understand how and when we engage the defined element, 00:04:02.680 --> 00:04:07.180 how does it fit in to consuming cloud services, 00:04:07.190 --> 00:04:08.560 and when is it useful? 00:04:09.240 --> 00:04:13.390 The pay‑as‑you‑go ability of measured first drew major businesses to 00:04:13.390 --> 00:04:16.950 consider consuming cloud services in the boardroom. 00:04:17.339 --> 00:04:20.750 It was compelling to be presented with the opportunity to 00:04:20.750 --> 00:04:23.590 reduce the capitalization of technology, 00:04:23.600 --> 00:04:27.560 which is the costliest element of any significant business. 00:04:28.340 --> 00:04:32.560 Now that we've covered the definition and the application of measured, 00:04:32.660 --> 00:04:36.950 let's consider what this concept could be integrated with. 00:04:37.840 --> 00:04:42.200 The integration comes when you can take one discrete exam item and make a 00:04:42.200 --> 00:04:47.450 seamless connection to another discrete exam item. For instance, how do we 00:04:47.460 --> 00:04:53.290 integrate measured with rapid elasticity in BRROM? The definition of rapid 00:04:53.290 --> 00:04:56.740 elasticity is a multidirectional function. 00:04:56.940 --> 00:05:01.610 We have the rapid expansion and scaling up of services and the 00:05:01.610 --> 00:05:04.760 immediate release of those services when no longer needed. 00:05:05.340 --> 00:05:09.880 An application of rapid elasticity is learning how to use the cloud for 00:05:09.890 --> 00:05:14.160 high‑velocity work in what is known as immutable workloads. 00:05:14.540 --> 00:05:18.990 These workloads are not maintained in how a datacenter server is 00:05:18.990 --> 00:05:23.130 maintained with care and feeding the patch management process. When 00:05:23.130 --> 00:05:26.140 we no longer need a workload in the cloud, 00:05:26.450 --> 00:05:27.460 you can delete it. 00:05:27.940 --> 00:05:32.510 You cannot delete a server in the datacenter. So, we have the 00:05:32.520 --> 00:05:37.880 application of rapid elasticity now. We want to integrate rapid 00:05:37.880 --> 00:05:43.540 elasticity with measured. The rapid release of the services no 00:05:43.540 --> 00:05:48.250 longer needed supports the measured attribute of only paying for the 00:05:48.250 --> 00:05:49.860 services that you are using. 00:05:50.340 --> 00:05:52.900 When you no longer use that service, 00:05:52.910 --> 00:05:59.000 you no longer pay for it. Join me in the following clip as we 00:05:59.000 --> 00:06:04.750 consider more specific strategies paired with sample questions 00:06:04.800 --> 00:06:07.460 to address navigating the exam.