1
00:00:00,046 --> 00:00:02,345
So we're looking at this massive pivot
point, right?

2
00:00:02,670 --> 00:00:08,115
The DoD drops this class deviation--what
was it, 2024-O0013?

3
00:00:08,626 --> 00:00:13,735
And suddenly, everybody who was scrambling
to figure out NIST SP 800-171 Revision 3

4
00:00:14,176 --> 00:00:14,687
is told...

5
00:00:14,803 --> 00:00:15,209
wait.

6
00:00:15,813 --> 00:00:16,405
Hold on.

7
00:00:17,009 --> 00:00:18,971
We are sticking with Revision 2 for now.

8
00:00:19,180 --> 00:00:23,534
It's a strategic pause, but it feels like
a pressure cooker because Revision 3 isn't

9
00:00:23,580 --> 00:00:25,705
actually going away, it's just...

10
00:00:26,146 --> 00:00:26,657
hovering.

11
00:00:26,917 --> 00:00:28,997
Hovering is a polite way to put it, Eric.

12
00:00:29,184 --> 00:00:31,957
It's more like a looming architectural
shift.

13
00:00:32,077 --> 00:00:38,997
The DoD issued that class deviation,
2024-O0013, back

14
00:00:39,050 --> 00:00:43,557
in May, specifically to prevent a
situation where contractors would be contractually

15
00:00:43,610 --> 00:00:47,397
bound to Rev 3 before the assessment
infrastructure was ready.

16
00:00:47,450 --> 00:00:52,117
If they hadn't, the moment Rev 3 went
final, standard DFARS clauses would have

17
00:00:52,157 --> 00:00:54,757
technically required immediate compliance.

18
00:00:54,777 --> 00:00:57,477
And let's be honest, nobody was ready for
that.

19
00:00:57,537 --> 00:01:01,237
But the mistake is thinking this pause
means you can just sit on your hands.

20
00:01:01,308 --> 00:01:03,944
Right, because Revision 3 is fundamentally
different.

21
00:01:04,269 --> 00:01:06,834
It's not just a minor patch, like a point
release.

22
00:01:07,159 --> 00:01:09,783
It completely restructures how the
controls work.

23
00:01:10,387 --> 00:01:14,752
I mean, they aligned it with NIST SP
800-53 Revision 5, right?

24
00:01:15,263 --> 00:01:18,815
And they got rid of the old distinction
between basic and derived security

25
00:01:18,885 --> 00:01:19,593
requirements.

26
00:01:20,034 --> 00:01:20,917
It's all just...

27
00:01:21,242 --> 00:01:22,600
security requirements now.

28
00:01:22,833 --> 00:01:23,633
Exactly.

29
00:01:23,713 --> 00:01:26,273
They collapsed that structural division.

30
00:01:26,353 --> 00:01:30,753
In Rev 2, you had basic requirements and
derived requirements,

31
00:01:30,793 --> 00:01:34,153
which honestly created this weird,
artificial hierarchy.

32
00:01:34,223 --> 00:01:39,073
Now, it's a flat structure, directly
mapped to the 800-53 catalog,

33
00:01:39,100 --> 00:01:41,313
which is the catalog federal agencies use.

34
00:01:41,413 --> 00:01:45,633
But the real kicker in Rev 3, the thing
that is going to give compliance managers

35
00:01:45,691 --> 00:01:49,153
nightmares, is the introduction of ODPs.

36
00:01:49,196 --> 00:01:51,233
Organization-Defined Parameters.

37
00:01:51,285 --> 00:01:52,109
ODPs.

38
00:01:52,713 --> 00:01:53,154
Right.

39
00:01:53,595 --> 00:01:56,126
I've heard this described as a
double-edged sword.

40
00:01:56,637 --> 00:02:00,631
On one hand, it gives flexibility, but on
the other hand, it means the government

41
00:02:00,677 --> 00:02:05,310
has to actually define those parameters,
or the contractor has to define them and

42
00:02:05,368 --> 00:02:06,308
get them approved.

43
00:02:06,749 --> 00:02:10,047
How does that actually play out in a
System Security Plan, an SSP?

44
00:02:10,292 --> 00:02:13,172
Well, think of an ODP as- as a
fill-in-the-blank.

45
00:02:13,359 --> 00:02:18,612
In Rev 2, a control might say, you know,
"restrict login attempts."

46
00:02:18,852 --> 00:02:25,412
In Rev 3, with ODPs, the control says
"restrict login attempts to

47
00:02:25,652 --> 00:02:31,652
[Organization-Defined: number] attempts
within [Organization-Defined: time

48
00:02:31,721 --> 00:02:33,012
period]."

49
00:02:33,052 --> 00:02:36,852
Now, if you're a defense contractor, you
can't just make those numbers up.

50
00:02:36,992 --> 00:02:43,572
The DoD has to- to issue a memorandum or a
guide specifying what those values are.

51
00:02:43,684 --> 00:02:49,252
They actually released a- a draft ODP
table, but- but until that's finalized and

52
00:02:49,305 --> 00:02:52,932
contractually binding, you have this- this
state of limbo.

53
00:02:53,172 --> 00:02:58,772
If you're updating your SSP today, you
have to maintain your current Rev 2 alignment

54
00:02:58,839 --> 00:03:03,812
while- while mapping out where these ODP
blanks are going to land in your future Rev

55
00:03:03,892 --> 00:03:04,612
3 state.

56
00:03:04,799 --> 00:03:06,932
It's- it's duplicate work, essentially.

57
00:03:06,952 --> 00:03:10,551
So they are basically giving contractors a
little bit of breathing room because of

58
00:03:10,586 --> 00:03:14,800
the supply chain complexity, but only for
those newly introduced controls.

59
00:03:15,404 --> 00:03:17,366
Everything else has to be green on day
one.

60
00:03:17,877 --> 00:03:23,462
That brings us to CMMC because they have
been telling everyone that CMMC 2.0 is

61
00:03:23,531 --> 00:03:24,832
based on Revision 2.

62
00:03:25,157 --> 00:03:29,882
If the FAR and DFARS transition to
Revision 3, what does that do to the CMMC

63
00:03:29,963 --> 00:03:30,497
rollout?

64
00:03:31,101 --> 00:03:35,536
We discussed this a bit during our CMMC
Unlocked episodes, but this feels like a

65
00:03:35,606 --> 00:03:37,057
major potential conflict.

66
00:03:37,292 --> 00:03:38,092
Well, they have to.

67
00:03:38,212 --> 00:03:40,092
And it's not just the ODPs.

68
00:03:40,232 --> 00:03:43,692
Rev 3 also introduces tailoring criteria.

69
00:03:43,852 --> 00:03:47,692
If you look at the assessment guide,
they've added new requirements around supply

70
00:03:47,745 --> 00:03:52,172
chain risk management, independent
assessments of security controls,

71
00:03:52,212 --> 00:03:53,852
and continuous monitoring.

72
00:03:53,952 --> 00:03:58,652
You are looking at a fundamental shift
from "static checklist compliance" to

73
00:03:58,732 --> 00:04:02,092
"active, risk-managed operational
security."

74
00:04:02,199 --> 00:04:06,892
It is going to force a lot of
small-to-mid-sized contractors to make hard choices

75
00:04:06,945 --> 00:04:08,732
about their IT investments.

76
00:04:08,796 --> 00:04:13,220
So, basically, they're attempting to align
the target, but because of how slow the

77
00:04:13,266 --> 00:04:17,562
bureaucracy moves, contractors are
essentially caught in the middle of a multi-year

78
00:04:17,620 --> 00:04:18,108
bridge.

79
00:04:18,711 --> 00:04:21,950
If you're a defense contractor right now,
what is the play?

80
00:04:22,461 --> 00:04:26,594
Do you start building to Rev 3 now, or do
you stick strictly to Rev 2 until the

81
00:04:26,629 --> 00:04:27,767
final rule drops?

82
00:04:27,958 --> 00:04:34,198
So- so the- the key thing to understand is
that CMMC is a- a vehicle for assessment,

83
00:04:34,238 --> 00:04:34,518
right?

84
00:04:34,545 --> 00:04:38,998
It- it doesn't actually write the security
standards; it- it verifies them.

85
00:04:39,198 --> 00:04:44,118
CMMC Level 2 is- is explicitly tied to
800-171.

86
00:04:44,198 --> 00:04:50,998
Because of that class deviation,
2024-O0013, the- the baseline for

87
00:04:51,078 --> 00:04:54,118
CMMC Level 2 remains Revision 2.

88
00:04:54,338 --> 00:04:55,478
For now.

89
00:04:55,598 --> 00:05:00,198
The- the final CMMC rule, which we've been
tracking in the 'c-m-m-c Unlocked'

90
00:05:00,267 --> 00:05:04,758
series, is moving through its own- its own
federal rulemaking process.

91
00:05:04,870 --> 00:05:10,198
Even when that CMMC rule goes final and
starts showing up in contracts,

92
00:05:10,225 --> 00:05:12,918
it's going to point to Rev 2 initially.

93
00:05:12,998 --> 00:05:18,678
But- but the DFARS rulemaking to- to
update the standard reference to Rev 3 is

94
00:05:18,718 --> 00:05:20,638
running on a- a parallel track.

95
00:05:20,705 --> 00:05:25,078
It's- it's like two trains running next to
each other, and- and at some point,

96
00:05:25,110 --> 00:05:26,198
they- they have to merge.

97
00:05:26,254 --> 00:05:30,608
This is exactly like what we talked about
in our "Pentagon Cyber Rules Reset"

98
00:05:30,643 --> 00:05:31,328
episode.

99
00:05:31,932 --> 00:05:36,912
The rulemaking process moves at a glacial
pace, but once those final rules drop,

100
00:05:37,121 --> 00:05:38,898
the clock starts ticking fast.

101
00:05:39,501 --> 00:05:44,691
For contractors listening, the takeaway is
clear: do not wait for the final rule to

102
00:05:44,749 --> 00:05:49,822
start looking at those
Organization-Defined Parameters and Revision 3 controls.

103
00:05:50,519 --> 00:05:51,773
Start mapping them now.

104
00:05:52,469 --> 00:05:55,929
Paul, thanks for breaking down these
complex requirements for us today.

105
00:05:56,083 --> 00:05:57,443
Potentially, yes.

106
00:05:57,534 --> 00:06:01,843
Though- though the DoD has indicated there
will be a- a phase-in period.

107
00:06:01,923 --> 00:06:04,483
They- they aren't going to pull the rug
out overnight.

108
00:06:04,563 --> 00:06:09,043
But- but this is why the strategic pause
on Rev 3 is- is so deceptive.

109
00:06:09,176 --> 00:06:11,524
It's not a- a pass to do nothing.

110
00:06:11,631 --> 00:06:13,764
It's a- a window of preparation.

111
00:06:13,977 --> 00:06:19,524
If you get certified under Rev 2, your-
your three-year certification cycle starts.

112
00:06:19,644 --> 00:06:23,924
But- but during those three years, you
will almost certainly have to transition your

113
00:06:23,977 --> 00:06:29,204
internal systems to meet Rev 3
requirements as new contracts get awarded with the

114
00:06:29,264 --> 00:06:30,964
updated DFARS clauses.

115
00:06:31,064 --> 00:06:36,244
You have to- you have to design your
systems today with the flexibility to- to adopt

116
00:06:36,284 --> 00:06:40,644
those Rev 3 ODPs without- without tearing
down your whole infrastructure.

117
00:06:40,660 --> 00:06:43,063
So- so what are the concrete next steps?

118
00:06:43,272 --> 00:06:47,394
If- if you're advising a defense
contractor right now, who's- who's caught in this

119
00:06:47,452 --> 00:06:50,017
interim phase, what do they actually do
tomorrow morning?

120
00:06:50,292 --> 00:06:54,292
First, do not halt your- your Rev 2
implementation.

121
00:06:54,399 --> 00:06:58,852
If you aren't fully compliant with Rev 2
today, you have zero chance of- of

122
00:06:58,908 --> 00:07:03,252
surviving the transition to Rev 3, let
alone a CMMC assessment.

123
00:07:03,392 --> 00:07:06,532
Get your Rev 2 SSP solid.

124
00:07:06,669 --> 00:07:12,372
Second, conduct a- a preliminary gap
analysis against the final draft of Rev 3.

125
00:07:12,492 --> 00:07:16,212
Focus heavily on those
Organization-Defined Parameters.

126
00:07:16,292 --> 00:07:21,412
Look at the- the draft ODP values the DoD
released and- and test your current

127
00:07:21,465 --> 00:07:22,932
configurations against them.

128
00:07:23,119 --> 00:07:29,572
If the DoD draft says "multifactor
authentication session termination after ,"

129
00:07:29,672 --> 00:07:34,372
and your current policy is eight hours,
look at- at what it takes to change that.

130
00:07:34,505 --> 00:07:39,012
Start testing those tighter configurations
now, in a- in a non-production

131
00:07:39,059 --> 00:07:41,732
environment, so you- you know what breaks.

132
00:07:41,796 --> 00:07:46,081
So they are running parallel processes,
which makes the timing even more critical.

133
00:07:46,591 --> 00:07:49,970
But what about the actual rollout period
once the rule is finalized?

134
00:07:50,481 --> 00:07:54,823
Do contractors get a grace period, or is
it an overnight shift to Rev 3?

135
00:07:55,274 --> 00:07:56,314
Always a pleasure, Eric.

136
00:07:56,394 --> 00:07:57,674
Stay secure out there.

