That having been said (and assuming my one-sentence summary is not overly simplified as relates to this question), I would have to say that the answer depends heavily on three things: the type of business you are in; the physical vulnerability of your cable plant; and the opinion of your compliance officer. Let me elaborate on my thinking, since I don't think there is an "absolute" answer to this.
I presume when you say "intelligent cabling solution" you are referring to one of the cable/connector manufacturers using something like an "iTRACS" type patch tracking approach. The potential advantage I see would be the ability to demonstrate to an auditor that no "confidential" information has been routed to an unauthorized user by means of inappropriate patching. If you are in a business where that kind of thing might be of concern and your physical security at patch points could be compromised (like you're sharing IDF rooms with other services) and someone might call this into question, then such a solution might make you look really good one day when the auditors come to call. Good audit trails, after all, seem to be one of the tenets of SOX compliance. There are a number of other potential IT management advantages to intelligent patching, along with the bothersome aspect of the special patch cables. But from the SOX standpoint, I think this is a decision that should be reached jointly between IT and Compliance after a thorough discussion of any physical vulnerabilities that exist, and the factors that prevent addressing them in any other way.
It might also be of interest to note that Belden has recently announced a patching solution that both color-codes and "keys" six different LC-type fiber jack versions so that one color cannot be patched into another. This won't do much for the station cable, which is still mostly UTP, but if you are dealing with a sufficiently high level of data security to justify separate switches for restricted network segments, this could help protect the optical side of your network from cross-patching as well.
This was first published in November 2005