De-perimeterization is a crock...
"De-perimeterization" is popular among the VPN, application protection, and web services communities. It's another in the never-ending stream of labels that marketing wonks invent to distinguish what they are trying to sell from what everyone else is selling. It's a dumb and inaccurate term that only serves to confuse buyers, which ultimately causes them to buy badly, or not buy at all. De-perimeterization is a testimony to the shortcomings of a society that operates on ten-word sound bites.
De-perimeterization is "a worldwide push toward a more porous corporate shell yet more secure collaborations in our increasingly interconnected online world"1. De-perimeterization is yet another forecast of the demise of the corporate perimeter, the traditional network firewall, in this case due to the increased employment of web services in collaborative networking: simply put, not only people but executable code (services) move across enterprises, mostly over web, and hence through ports that network firewalls allow inbound and outbound.
What the term tries to convey can't easily be done in one word. What the term and the hype woefully misrepresent spreads the F.U.D.
De perimeter exists. You've misappropriated the prefix de.
There are many perimeters in the present and future enterprise. The perimeter that that de-perimeterization tries to deprecate is maintained through network layer firewalls. It's not going away. It's now decentralized through the use of personal, teleworker, and small office firewalls as complements to enterprise Internet-facing and compartmental firewalls.
Further complementing the network layer perimeter is a perimeter of application protection. This additional layer of security will be responsible for assuring that application connections are authenticated and that the data conveyed over them is authentic and (where appropriate) confidential. And by this, I don't mean "VPN".
The column I cited earlier casts skepticism on de-perimeterization's ultimate goal: "worldwide use of system-, data- and connection-level authentication". While I hate the term, I love the objective. What is often misunderstood when we use the word data is that data includes identities, information web services process and and the executable code (services) organizations exchange, as well as the channels over which this data are communicated. This is not de-perimeterization at all, but the addition of federated identities to our existing layers of security.
We don't need a new term. We need people to RTFM and use the terms we have appropriately.
Archived at http://www.securityskeptic.com/arc20040901.htm#BlogID303
by Dave Piscitello