WEBVTT

00:00:00.017 --> 00:00:03.192
Hey everybody and welcome back to the Operational ITAM podcast.

00:00:03.494 --> 00:00:08.347
I'm Bill Van Nort and this is episode 3, the one I told you to bring your skepticism to.

00:00:08.869 --> 00:00:12.587
I hope you packed it because today we cross over to the intangible side of the

00:00:12.587 --> 00:00:17.902
house, software asset management, licenses, entitlements, audits,

00:00:18.064 --> 00:00:20.380
and the publishers who profit from your confusion.

00:00:20.996 --> 00:00:24.734
If you're joining us for the first time, welcome. Genuinely glad you're here.

00:00:25.338 --> 00:00:29.128
I'd suggest starting with episodes one and two, because we build on each other around here.

00:00:29.662 --> 00:00:34.005
But if you want to jump in the deep end with us today, hey, I admire the confidence. Come on in.

00:00:34.719 --> 00:00:38.670
Good morning, good afternoon, or good evening, wherever you happen to be listening from.

00:00:39.169 --> 00:00:43.307
This is the operational ITAM podcast, the show where we take the unglamorous

00:00:43.307 --> 00:00:46.448
machinery of enterprise technology and make it make sense.

00:00:47.110 --> 00:00:51.635
I'm your host, Bill, and today's episode might be the most expensive one we ever do.

00:00:52.251 --> 00:00:56.035
Not for you, for the publishers, once you learn what I'm about to teach you.

00:00:56.680 --> 00:01:00.447
Welcome in. Grab your coffee, grab your headphones, and let's get into it.

00:01:01.115 --> 00:01:05.527
So, last episode we walked the hardware lifecycle gate by gate.

00:01:06.008 --> 00:01:10.757
Seven gates, seven failure modes, one discipline. Custody.

00:01:11.633 --> 00:01:13.590
The record follows the asset.

00:01:14.478 --> 00:01:20.469
And here's the thing about hardware. For all its problems, hardware has one enormous advantage.

00:01:21.038 --> 00:01:25.583
You can touch it. You can put a tag on it. You can, in a pinch,

00:01:26.053 --> 00:01:28.276
walk into a stock room and count it.

00:01:28.868 --> 00:01:33.373
Software has none of those advantages. You can't touch it. You can't tag it.

00:01:34.064 --> 00:01:37.448
And here's the part that changes everything. You don't even own it.

00:01:38.197 --> 00:01:41.680
Let me say that again because it's the foundation of this entire episode.

00:01:42.295 --> 00:01:47.682
When your company buys software, it does not buy software. It buys a right.

00:01:48.408 --> 00:01:53.995
A narrowly defined, contractually bounded, publisher-authored right to use software

00:01:53.995 --> 00:02:00.033
in a specific way, measured by a specific metric, under conditions written by the seller's lawyers.

00:02:00.910 --> 00:02:05.774
That document is called a license, and the rights it grants you are called entitlements.

00:02:06.610 --> 00:02:10.540
And the distance between what you're entitled to do and what you're actually doing?

00:02:11.161 --> 00:02:15.225
That distance is measured in dollars, sometimes millions of them.

00:02:16.229 --> 00:02:20.875
I know because I've recovered millions of them, and I've watched other organizations

00:02:20.875 --> 00:02:27.282
pay millions of them to publishers at settlement tables with very unhappy CFOs in the room.

00:02:27.915 --> 00:02:30.028
So today we're learning to measure that distance.

00:02:33.487 --> 00:02:36.506
Software Everything in this field gets a three-letter acronym,

00:02:36.767 --> 00:02:40.935
it's practically a bylaw, is the discipline of managing software entitlements

00:02:40.935 --> 00:02:42.525
and software deployments across

00:02:42.525 --> 00:02:46.073
their lifecycle, and continuously reconciling one against the other.

00:02:47.025 --> 00:02:51.580
Hardware Asset Management was a custody discipline. Software Asset Management

00:02:51.731 --> 00:02:54.941
is a bookkeeping discipline. And I mean that literally.

00:02:56.098 --> 00:02:58.559
Here's the mental model I want you to carry out of this episode.

00:02:59.029 --> 00:03:02.408
Picture an old-fashioned ledger. Double entry. Two columns.

00:03:02.872 --> 00:03:06.796
On the left side, everything you're entitled to use. On the right side,

00:03:07.069 --> 00:03:08.520
everything you're actually using.

00:03:09.066 --> 00:03:13.391
SAM is the practice of keeping both columns accurate and comparing them. Constantly.

00:03:13.838 --> 00:03:18.243
That comparison has a formal name. The Effective License Position, or ELP.

00:03:19.120 --> 00:03:22.873
Write that down, because the ELP is to software what the physical inventory

00:03:22.873 --> 00:03:25.674
count is to hardware. It is the moment of truth.

00:03:26.992 --> 00:03:31.653
Let's build the ledger, one side at a time. Side 1. Entitlements.

00:03:32.071 --> 00:03:33.493
What you have the right to use.

00:03:34.097 --> 00:03:37.470
An entitlement is born the same place a hardware asset record is born.

00:03:37.859 --> 00:03:40.123
Remember gate 2? At the purchase.

00:03:40.790 --> 00:03:43.402
But an entitlement is more demanding than a hardware record,

00:03:43.664 --> 00:03:46.205
because an entitlement is only as good as its proof.

00:03:46.989 --> 00:03:51.389
Here's what must be captured. The product. The version and addition.

00:03:51.993 --> 00:03:56.782
The quantity. The license metric. Hold that thought. We're coming back to metrics.

00:03:57.443 --> 00:04:01.884
The purchase order, the agreement it was purchased under, the reseller,

00:04:02.534 --> 00:04:05.286
the dates, and the proof of purchase itself.

00:04:06.023 --> 00:04:10.331
Contracts, order forms, invoices, the actual paper.

00:04:11.108 --> 00:04:15.559
And here's how it fails. The proof is scattered. Some of it's in procurement

00:04:15.559 --> 00:04:19.270
system, some of it's in a filing cabinet from an acquisition eight years ago,

00:04:19.560 --> 00:04:22.039
some of it's in the inbox of a person who retired.

00:04:22.591 --> 00:04:25.987
I have personally watched a company repurchase licenses it already owned,

00:04:26.271 --> 00:04:30.677
paid twice for the same rights, because nobody could produce the evidence from the first purchase.

00:04:31.147 --> 00:04:34.804
In an audit, an entitlement you can't prove is an entitlement you don't have.

00:04:35.240 --> 00:04:38.717
The publisher's auditor is not going to take your word for it. Would you?

00:04:39.385 --> 00:04:44.103
Now, the metrics. This is where software licensing earns its reputation.

00:04:44.654 --> 00:04:49.219
Hardware gets counted in units. Simple. Software gets counted in whatever unit

00:04:49.219 --> 00:04:52.323
of measure the publisher's revenue strategy requires this year.

00:04:52.799 --> 00:04:57.843
Per device, per named user, per concurrent user, per processor,

00:04:58.215 --> 00:05:02.669
per core, and cores come with counting rules, and the counting rules come with

00:05:02.669 --> 00:05:05.465
exceptions, and the exceptions come with footnotes.

00:05:05.947 --> 00:05:10.659
Per server, per virtual machine, and the newest arrival, the one we'll talk

00:05:10.659 --> 00:05:15.635
about after the break, per employee, as in every single one,

00:05:15.908 --> 00:05:17.574
whether they use the product or not.

00:05:18.184 --> 00:05:21.759
Each metric is a different unit of measure, which means each product in your

00:05:21.759 --> 00:05:25.509
estate is being counted in a different currency, and your ledger has to speak

00:05:25.509 --> 00:05:27.338
all of them. That is the job.

00:05:28.035 --> 00:05:29.457
Nobody said it was a small one.

00:05:30.978 --> 00:05:34.345
Side 2. Deployments. What you're actually using.

00:05:35.053 --> 00:05:39.569
This side of the ledger comes from discovery. Your endpoint management platform.

00:05:40.109 --> 00:05:45.007
Your server inventory. Your cloud consoles. Telling you what's installed and running.

00:05:45.919 --> 00:05:50.177
And if you remember episode 1, I told you your endpoint management platform

00:05:50.177 --> 00:05:51.544
already knows what's connected.

00:05:52.188 --> 00:05:55.213
That's still true, and this is where that data goes to work.

00:05:55.863 --> 00:06:00.838
But raw discovery data is a crime scene. It has to be normalized before it means anything.

00:06:01.616 --> 00:06:05.407
Here's what I mean. Ask a discovery tool what's installed, and it will tell

00:06:05.407 --> 00:06:07.461
you the same product 40 different ways.

00:06:07.867 --> 00:06:11.449
Different casing, different version strings, different bundle names,

00:06:11.664 --> 00:06:13.400
publisher names spelled six ways.

00:06:14.207 --> 00:06:19.884
Normalization is the unglamorous, essential work of translating that chaos into a clean statement.

00:06:20.517 --> 00:06:24.940
This product, this edition, this version, this many installs.

00:06:25.625 --> 00:06:29.642
No normalization, no ledger. Just noise with a user interface.

00:06:30.600 --> 00:06:35.575
And there's one more layer, and it's where the money hides. Installed is not the same as used.

00:06:35.795 --> 00:06:39.577
A copy of an expensive engineering application sitting untouched on a laptop

00:06:39.577 --> 00:06:43.479
for 11 months is a deployment on your ledger and a waste in your budget.

00:06:44.587 --> 00:06:49.056
Metering, measuring actual usage, not just presence, is how you find those.

00:06:49.544 --> 00:06:54.124
Remember the ghost from episode 2? Records without devices, still drawing a salary?

00:06:54.589 --> 00:06:58.942
Software has ghost too. We call it shelfware. Licenses purchased,

00:06:59.111 --> 00:07:01.044
deployed maybe, used never.

00:07:01.468 --> 00:07:04.909
Hold that thought too, because after the break, I'm going to put numbers on

00:07:04.909 --> 00:07:07.000
it. And the numbers are worse than you think.

00:07:07.731 --> 00:07:10.872
So entitlements on the left, normalized deployments on the right.

00:07:11.290 --> 00:07:15.881
Now the reconciliation. product by product, metric by metric, you compare.

00:07:16.613 --> 00:07:20.833
Three outcomes are possible. Outcome one, the columns balance.

00:07:21.367 --> 00:07:23.352
Enjoy the moment, frame it.

00:07:24.177 --> 00:07:28.217
Outcome two, you're over-licensed. You own more than you use.

00:07:28.983 --> 00:07:33.082
That's shelfware, and it's not a compliance problem, it's a savings problem.

00:07:33.859 --> 00:07:37.169
Those are dollars on the table at your next renewal, if you have the data to

00:07:37.169 --> 00:07:39.083
prove it, and the spine to act on it.

00:07:39.785 --> 00:07:44.133
Outcome three, you're under licensed. You're using more than you own.

00:07:44.748 --> 00:07:49.764
That's a compliance gap. And a compliance gap is a debt. You may not know the amount yet.

00:07:50.362 --> 00:07:53.537
You may not know the due date, but somebody is going to collect it.

00:07:53.856 --> 00:07:56.329
And next, I'll introduce you to the collectors.

00:07:57.008 --> 00:08:00.169
If you're enjoying the show, do me a favor, like and subscribe,

00:08:00.169 --> 00:08:04.027
post your comments, and share this one with whoever handles your next software renewal.

00:08:04.503 --> 00:08:08.386
Trust me, they either already know all this, or they really need to.

00:08:09.060 --> 00:08:11.927
Alright, now on to the collectors. Let's talk about audits.

00:08:12.746 --> 00:08:16.669
Here's the fact of life. Nobody puts on the sales slide. Buried in virtually

00:08:16.669 --> 00:08:20.095
every enterprise software agreement you have ever signed is an audit clause.

00:08:20.472 --> 00:08:24.054
It grants the publisher the right to verify your usage against your entitlements,

00:08:24.414 --> 00:08:29.661
usually with 30 or 45 days' notice, sometimes through a designated third-party audit firm.

00:08:30.155 --> 00:08:34.056
You agreed to it. Everyone agrees to it. It's about as negotiable as gravity.

00:08:34.793 --> 00:08:39.529
And here's my opinion, clearly labeled as an opinion, per the House rules,

00:08:40.051 --> 00:08:42.907
though it's an opinion with three decades of scar tissue behind it.

00:08:43.795 --> 00:08:49.728
For certain publishers, the audit is not a compliance function. It's a sales function.

00:08:50.471 --> 00:08:55.016
The audit letter arrives, mysteriously, in the quarter before your renewal.

00:08:55.742 --> 00:09:00.084
The findings arrive with an eye-watering number attached. And then,

00:09:00.444 --> 00:09:04.367
what a coincidence, the number can shrink dramatically if you'd like to sign

00:09:04.367 --> 00:09:08.490
a bigger agreement, a longer term, maybe a nice cloud commitment.

00:09:09.140 --> 00:09:12.907
That's not an audit. That's a negotiation that opens with a subpoena.

00:09:13.645 --> 00:09:16.454
I've survived audits from the biggest publishers on the planet.

00:09:16.745 --> 00:09:19.868
I'll teach you the full defense playbook in an upcoming two-parter,

00:09:20.030 --> 00:09:22.677
from the moment the letter lands to the handshake at settlement.

00:09:23.072 --> 00:09:27.007
Today, I just need you to understand the exposure. And there is no better teacher

00:09:27.007 --> 00:09:30.949
right now than two current events. Skepticism ready? Good.

00:09:31.623 --> 00:09:35.767
Current event number one, Oracle and Java. For most of its life,

00:09:35.767 --> 00:09:39.290
Java was treated like air, free, everywhere, unremarkable.

00:09:39.609 --> 00:09:42.430
It's in your applications, your appliances, your middleware,

00:09:42.605 --> 00:09:44.712
tucked into installers nobody remembers running.

00:09:45.083 --> 00:09:50.105
Then the licensing changed, and in 2023, it changed in a way this industry had never seen.

00:09:50.459 --> 00:09:55.341
Oracle moved Java to what they call the Java SE Universal subscription, priced per employee.

00:09:55.718 --> 00:10:00.199
Not per user of Java, not per installation, per employee, full-time,

00:10:00.368 --> 00:10:05.180
part-time, contractors, everyone on the roster, whether they've ever touched Java or not.

00:10:05.906 --> 00:10:10.381
Sit with that math. 10,000 employees and 100 servers running Java?

00:10:10.927 --> 00:10:12.431
You're paying for 10,000.

00:10:13.028 --> 00:10:16.465
The install count is almost irrelevant. The head count is the meter.

00:10:17.005 --> 00:10:20.906
It is the most aggressive metric change in enterprise software in my three decades,

00:10:21.260 --> 00:10:24.911
and right now, this year, the enforcement wave is cresting.

00:10:25.596 --> 00:10:30.037
The friendly emails asking to discuss your Java usage have matured into formal

00:10:30.037 --> 00:10:33.535
audit letters, addressed to CIOs and CFOs by name.

00:10:34.314 --> 00:10:36.648
And here's the detail that should raise the hair on your neck.

00:10:37.106 --> 00:10:39.991
One known trigger is Oracle's own download logs.

00:10:40.577 --> 00:10:43.306
They know which companies downloaded Java from their website.

00:10:43.833 --> 00:10:45.470
They've had years to gather that data.

00:10:46.080 --> 00:10:49.291
The letter isn't a fishing trip. They already know the fish is in the boat.

00:10:49.889 --> 00:10:54.324
Now the SAM response, and notice it's just our ledger doing its job.

00:10:55.124 --> 00:11:00.898
Right column first. Discover every Java installation in the estate and identify

00:11:00.898 --> 00:11:02.630
which distribution it is,

00:11:03.135 --> 00:11:08.578
because Oracle's JDK is licensable, and the open-source OpenJDK builds from

00:11:08.578 --> 00:11:10.166
other providers are not.

00:11:10.885 --> 00:11:15.755
That distinction is the entire ballgame, and it lives in your normalization data.

00:11:16.887 --> 00:11:21.015
Then the left column. What, if anything, are you entitled to?

00:11:21.996 --> 00:11:26.038
And then the strategic decision, because for a lot of organizations,

00:11:26.038 --> 00:11:28.887
the honest answer to this metric is an exit.

00:11:29.665 --> 00:11:34.684
Migrate to a supported OpenJDK distribution, document the migration,

00:11:35.119 --> 00:11:40.854
and decline to pay a per-employee toll for a runtime that lives on a minority of your machines.

00:11:41.661 --> 00:11:48.209
That's not a loophole, that's asset management. Current event number two, Broadcom and VMware.

00:11:48.813 --> 00:11:53.228
If your data center runs VMware, and statistically it does, you already know

00:11:53.228 --> 00:11:56.441
this story, probably from painful first-hand experience.

00:11:57.236 --> 00:12:02.490
Broadcom acquired VMware and, in short order, ended perpetual licensing entirely.

00:12:03.204 --> 00:12:07.975
Subscription only. 160 products collapsed into a handful of bundles.

00:12:08.591 --> 00:12:12.265
Pricing moved to per core, with a 16 core minimum per processor,

00:12:12.660 --> 00:12:15.034
whether your processor has 16 cores or not.

00:12:15.952 --> 00:12:19.784
Customers opening renewal quotes have reported multiples, not percentages,

00:12:19.999 --> 00:12:22.106
multiples of their previous costs.

00:12:22.936 --> 00:12:27.074
And customers running on old perpetual licenses with expired support have received

00:12:27.074 --> 00:12:28.857
cease and desist letters over patches.

00:12:29.755 --> 00:12:33.662
Audit activity is up. Compliance reporting obligations are tighter.

00:12:34.469 --> 00:12:39.543
Here's the lesson, and it's bigger than either vendor. The metric can change underneath you.

00:12:39.816 --> 00:12:43.834
You can be perfectly compliant, perfectly optimized, and a strategy decision

00:12:43.834 --> 00:12:47.826
in someone else's boardroom redraws your entire cost model overnight.

00:12:48.134 --> 00:12:52.308
Java's meter became your org chart. VMware's meter became your core count,

00:12:52.621 --> 00:12:54.102
with a minimum you don't control.

00:12:54.450 --> 00:12:58.450
The only defense is the ledger. Know your entitlements, know your deployments,

00:12:58.653 --> 00:13:02.246
know your contract terms, before the letter arrives.

00:13:02.635 --> 00:13:06.834
Because every one of these situations is negotiable, but only for the customer

00:13:06.834 --> 00:13:08.225
who shows up with evidence.

00:13:08.602 --> 00:13:13.061
The customer who shows up with a shrug pays list price, or worse.

00:13:13.670 --> 00:13:18.154
One more stop before we close the ledger, SaaS. Because I can hear somebody

00:13:18.154 --> 00:13:21.228
out there saying, Bill, this is all legacy stuff.

00:13:21.611 --> 00:13:25.808
We're a cloud company. We subscribe to everything. Audits can't touch us.

00:13:26.395 --> 00:13:30.225
Congratulations. You've traded the compliance problem for a waste problem,

00:13:30.503 --> 00:13:32.158
and the waste problem might be bigger.

00:13:32.796 --> 00:13:36.744
Here's the current state of play, and these numbers are recent research, not folklore.

00:13:37.400 --> 00:13:41.086
The average organization now runs roughly 300 SaaS applications.

00:13:41.643 --> 00:13:46.934
Industry studies put unused or underutilized SaaS licenses somewhere between 30 and 50 percent.

00:13:46.934 --> 00:13:52.164
One 2026 analysis found the average organization actively using barely half

00:13:52.164 --> 00:13:56.114
the licenses it pays for, with the waste at large enterprises measured in the

00:13:56.114 --> 00:13:57.816
tens of millions of dollars.

00:13:58.379 --> 00:14:01.810
Per year. Per company. Where does it come from?

00:14:02.681 --> 00:14:06.576
You already know, because it's the same failure modes wearing new costumes.

00:14:07.493 --> 00:14:12.375
Remember gate six, recovery, the most broken stage in the hardware life cycle?

00:14:13.205 --> 00:14:18.061
The employee leaves, the laptop never comes back? Same thing happens with SaaS

00:14:18.061 --> 00:14:21.831
seats, except worse, because there's no physical object to miss.

00:14:22.702 --> 00:14:27.591
The person departs, the single sign-on gets disabled, and the 11 paid subscriptions

00:14:27.591 --> 00:14:30.154
attached to that person just keep renewing.

00:14:30.862 --> 00:14:32.790
Quietly. Forever.

00:14:33.707 --> 00:14:36.521
That's a ghost with a credit card. And Shadow IT.

00:14:37.265 --> 00:14:41.511
Remember the request that happens outside the process? A department swipes a

00:14:41.511 --> 00:14:46.524
card, a tool appears, it auto-renews for years, and your ledger never hears about it.

00:14:47.314 --> 00:14:52.191
The fix is not exotic. Tie license recovery to offboarding, the same way we

00:14:52.191 --> 00:14:54.013
tied device recovery to offboarding.

00:14:54.512 --> 00:14:57.473
No departure ticket closes until the seats are reclaimed.

00:14:58.082 --> 00:15:00.387
Meter actual usage before every renewal,

00:15:00.764 --> 00:15:04.189
and walk into that renewal with utilization data instead of vibes.

00:15:04.961 --> 00:15:10.139
30% of your seats untouched in 90 days is not trivia. It's your negotiating position.

00:15:10.836 --> 00:15:14.986
Alright, let's extend the library one more time because it's earned its place on this show.

00:15:15.462 --> 00:15:19.665
If the estate is a library, then software is the strangest section in the building,

00:15:20.112 --> 00:15:21.755
because none of these books are yours.

00:15:22.573 --> 00:15:25.357
Every volume on these shelves is on loan from the publisher,

00:15:25.532 --> 00:15:26.989
and every loan has terms.

00:15:27.633 --> 00:15:31.789
Some books you can lend to anyone in the building. Some are chained to a single desk.

00:15:32.329 --> 00:15:35.631
Some are priced by how many people work in the building, whether they read or

00:15:35.631 --> 00:15:39.673
not. And yes, that's as absurd in the library as it is in your data center.

00:15:40.595 --> 00:15:44.552
Entitlements are the loan agreements in the file cabinet. Discovery is walking

00:15:44.552 --> 00:15:46.359
the shelves to see what's actually there.

00:15:46.963 --> 00:15:51.842
The ELP is comparing the two. And an audit? An audit is the publisher walking

00:15:51.842 --> 00:15:55.972
in unannounced, asking to see the file cabinet, and charging you retroactive

00:15:55.972 --> 00:15:58.787
late fees for every book you can't produce paperwork for.

00:15:59.693 --> 00:16:03.838
The books were never yours, the records are. Guard them accordingly.

00:16:04.691 --> 00:16:08.935
One closing principle, in the spirit of the ones that closed the last two episodes.

00:16:09.503 --> 00:16:13.306
Hardware asset management is a custody discipline. At every moment,

00:16:13.532 --> 00:16:17.033
one accountable party holds the asset, and the record says so.

00:16:17.601 --> 00:16:21.842
Software asset management is an evidence discipline. At every moment,

00:16:21.842 --> 00:16:26.182
for every product, you can produce proof of what you own and proof of what you're

00:16:26.182 --> 00:16:28.461
using, and you know the difference between them.

00:16:29.042 --> 00:16:33.942
Custody for the tangible. Evidence for the intangible. Every audit you'll ever

00:16:33.942 --> 00:16:36.553
face. Every renewal you'll ever negotiate.

00:16:37.012 --> 00:16:38.713
Every dollar you'll ever reclaim.

00:16:39.317 --> 00:16:43.903
All of it resolves to those two proofs. Keep the ledger and the ledger keeps you.

00:16:44.576 --> 00:16:46.979
Class dismissed. And here's your homework.

00:16:47.682 --> 00:16:51.983
This one has a due date and the due date is before Oracle's letter shows up.

00:16:52.796 --> 00:16:57.794
Pick one publisher. Just one. And if you can't decide, make it Java.

00:16:58.775 --> 00:17:04.392
This week, pull two lists. List one. Every installation of that publisher's

00:17:04.392 --> 00:17:06.490
products your discovery tools can see.

00:17:07.546 --> 00:17:12.505
List 2. Every entitlement you can actually prove. Real documents,

00:17:12.505 --> 00:17:15.284
in hand. Not, I think we bought that.

00:17:16.202 --> 00:17:21.692
Put them side by side. One product, one row. One honest comparison.

00:17:22.743 --> 00:17:26.104
That's your first effective license position, and I promise you,

00:17:26.388 --> 00:17:31.479
it will teach you more about your program in one page than any maturity assessment ever will.

00:17:32.385 --> 00:17:37.865
If the columns balance, congratulations, and frankly, I'd like to shake your hand.

00:17:38.758 --> 00:17:43.617
If they don't, well, now you know which episodes are coming next.

00:17:44.279 --> 00:17:49.215
And that's exactly the tease. Next episode, we begin the audit defense two-parter

00:17:49.215 --> 00:17:50.862
I promised back in episode one.

00:17:51.448 --> 00:17:57.665
The letter has landed. It's addressed to your CIO. The publisher wants an answer in 45 days.

00:17:58.182 --> 00:18:01.526
What you do in the first week determines what you pay in the last one.

00:18:02.019 --> 00:18:05.885
And almost everybody plays that first week wrong. Do not miss it.

00:18:06.483 --> 00:18:11.098
That's today's episode. You now understand the ledger, entitlements on the left,

00:18:11.499 --> 00:18:14.244
deployments on the right, and the truth in between.

00:18:15.185 --> 00:18:19.918
That's software asset management. Not all the details, but enough to be dangerous

00:18:20.138 --> 00:18:21.386
in the best possible way.

00:18:22.135 --> 00:18:27.156
I'm Bill Van Nort. This is the Operational ITAM Podcast. Keep your receipts,

00:18:27.331 --> 00:18:29.513
and I'll talk to you next week. Take care.