Hello again, and apologies for taking so long between posts. It can be fun to be released from the strict structural rules of research writing and roam, so I should be writing more of these posts, not less.
I was looking forward to doing some alliterative but also (I hope) meaningful observations about IAM, a challenging task but infinitely rewarding for an organization like Gartner that works hard to bring specific meaning to words. I thought I would express a view about identity and access management that might not be immediately obvious unless you step back some from the pipes, pumps and process nature of IAM to see a bigger pictures. Let’s look at it from a hypothetical historical perspective.
In the big scheme of things, IAM performs tasks that are very old, dating back even to the Middle Ages and before. Think of IAM as a person with four ‘personalities’: a soldier, a servant, a spy and a sage. Now what does this mean beyond the supposedly clever use of words that begin with ’s’?
As a soldier in medieval times, IAM established a means of protection for access to the keep, a way to control who came into the keep and who didn’t. A guard at the gate had to ‘identify’ those who wished to enter, and either grant or deny their access. One could have considered a soldier an “access manager”, when they were performing guard duties not off in battle somewhere.
As a servant, IAM also established a means of administering access. If new people never before seen needed access to the keep, the IAM servant ‘updated the access scrolls’ for those who were and were not permitted access. If residents left, the servant had to close up their homes and remove them from the access scrolls. If the prince was promoted to king, that had to be noted as well, since kings might be able to use the ‘other’ gate into the keep to avoid the peasant traffic in the main gate.
As a spy, IAM would provide a means to watch carefully the coming and going of residents, note suspicious patterns and report them. They also had to provide the scrolls for resident populations to the tax collector (kind of like a regulator for compliance, eh?), and otherwise provide careful oversight of the populations that lived within the keep. They might even spy on neighboring keeps to determine who had and had not visited their own.
Finally, IAM might have been a sage as well, providing analysis and insight into the information about who came and who went, assessing patterns of behavior, recommending which scrolls of access be combined for collective wisdom about the flow of humanity and goods into the keep. A sage would have reported to the king based on what they had discovered, which could raise or lower taxes, expand the gate or restrict access, and provide an overall view of what was happening regarding the identity of those at the keep.
IAM isn’t a new idea– it just has a different way today of being a soldier, a servant, a spy and/or a sage.
3 responses so far ↓
1 Dave Kearns // Sep 7, 2009 at 12:52 pm
Good analogy, Earl, but you could have gone back much farther than the middle ages I’d think – the first tribal/clan groupings relied on IAM techniques (especially biometrics) for access control. And the penalty for forgetting the “password” was pretty severe!
-dave
2 Earl Perkins // Sep 7, 2009 at 2:30 pm
Good point re: the penalty Dave, and you’re right, I could have gone much further back to illustrate similar points. It wasn’t so much a history lesson however in when identity management first started as it was simply a view of how it might be functionally considered, an analogy with historical implications.
3 Evolving IAM: Soldier, Servant, Spy and Sage | Spy sweeper up date today // Sep 7, 2009 at 4:15 pm
[...] and feat of residents, state suspicious patterns and inform them. Go here to feature the rest: Evolving IAM: Soldier, Servant, Spy and Sage Posted in Uncategorized | Tags: also-had, and-going, carefully-the-coming, coming, iam, [...]
Leave a Comment