Discussion about this post

User's avatar
Austin Marton's avatar

You ask some interesting questions which I think only the future can answer so let's see. . . The leap I am struggling to make with you is that a consultant with Claude is still a consultant with Claude. Getting Claude does not suddenly get you (the consultant) access to your client's proprietary internal data let alone a non-client's data. Every client serving project I ever worked on as a consultant always came with a tightly scoped data request vs. an open to all fishing expedition.

I would also put my money on most decent CFO's being in Krishna Rao's camp or figuring out how to be in his camp when it comes to the use of Claude etc. which I think approximates to your 2nd question to ponder over the weekend.

As a follow on I wonder now many CFO's, Audit Committees and Boards will actually tighten access to their data because of Claude and its ilk? If not because of Claude then probably because they may not trust their data in the hands of their auditor/external advisor in any event: https://www.afr.com/companies/professional-services/kpmg-audit-leaks-scandal-everything-you-need-to-know-20260606-p604i5.

The referenced article is how KPMG in Australia have been behaving with the confidential information of its clients' data and this is even without Claude as an accessory before, during or after the fact. I imagine this sort of behaviour is not restricted to Australia either.

No posts

Ready for more?