Tuesday March 27, 2007
Dave's Bit BucketDave Walker's jottings - mostly pertaining to security A disclosure state machine for Robin Robin Wilton blogged recently on "breach notification, UK style", and was scratching his head regarding how to determine the source of a leak if you have to make multiple disclosures. I think I have an answer, although it involves a lot more housekeeping and records management on the part of the person managing the disclosure. In short:
As Robin adds, "There's also a very predictable short-term consequence, which is that if you include the bogus records, you'll get a deluge of fraud allegations from the Audit Commisson because you appear to have a load of non-existent people on your payroll - with bank details and everything." As usual, he's quite right. I suspect that persuading the Audit Commission to accept and approve the concept of bogus records would be "difficult" to say the least, but things may well have to go that way. Maybe a better way to do "Full Disclosure" to the Audit Commission in particular when they decide to land on you, would be to send a separate and differently-protected disclosure to them, saying "and these are the bogus records in the main disclosure we just sent you"? Robin thinks that this is very much "swings and roundabouts" - I'm more inclined to see it as "turtles all the way down" :-). (2007-03-27 03:05:32.0) Permalink Comments [0] |
Calendar
RSS Feeds
All /Cooking /General /Java /Networking /Security Search | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||