In my previous blog, I argued that marketing’s speed problem is really an access problem, and that giving marketing a fast, sanctioned path to the tools it needs does more for governance than any other policy will. Solving that surfaces the harder question underneath it, which is what people are actually producing inside those tools.
This is where the conversation between IT and marketing usually breaks down, because both sides assume the other has it covered. Adobe Creative Cloud for enterprise Edition 4 is the clearest answer I’ve seen to this, though the controls only help if someone decides who they apply to, and that decision needs both functions in the room.
I’d ask IT to consider marketing a security stakeholder rather than a security risk, because we hold more sensitive material than most people assume.
We hold unreleased campaigns and product launches, as well as customer data within segmentation and personalisation workflows. We store contracted imagery and footage with licensing terms attached, executive photography, partner material under agreement, and original creative representing years of investment. Any of that leaking early causes commercial damage, and some of it causes contractual damage.
We also hold the relationships that make governance work. If your access controls and AI policies arrive as an edict, they get worked around. If they arrive as something marketing helped design, they get defended internally because marketing leadership has a stake in them holding.
In the OAIC’s most recent detailed breakdown, human error accounted for 37 per cent of all notifiable data breaches in Australia, up from 29 per cent in the previous six months. These are ordinary working days, when the wrong file goes to the wrong person or an account nobody thought about remains open. Creative workflows generate many such ordinary working days, which is exactly why marketing belongs inside your controls.
For most of my career, brand governance was a marketing housekeeping concern. We maintained guidelines, policed logo usage and occasionally had an uncomfortable conversation with a regional team about a template. None of it tended to land on IT’s desk, though generative AI has since collapsed that divide.
When a marketer uses a generative tool, several things happen at once, all squarely in IT’s territory. Material is pasted into a prompt, and depending on the tool, it may include unreleased campaign work, pricing, customer data or a product or service that hasn’t been announced. A model produces an output whose training provenance may be unclear, and that output then enters the market under your organisation’s name.
So the governance questions have moved beyond who can access the asset library to include:
Marketing can’t answer most of those questions, yet it’s generating the exposure daily while the answers are worked out.
Adobe Creative Cloud for enterprise Edition 4 addresses the first three points by letting administrators define which AI models and services are available to which groups of users, alongside the apps themselves, and ensuring your data isn’t used to train models. Your AI policy stops being a document people are asked to remember and becomes a configuration they work within. On the fourth point, Adobe extends IP indemnification to content generated through Firefly and to Adobe Stock assets, subject to the terms of your agreement. This means part of the copyright exposure is shifted onto a vendor that has chosen to carry it.
There’s a second-order effect to consider as well. When every person on a team can generate assets instantly, brand consistency shifts from a discipline problem to a volume problem. Guidelines assume a review step, yet at current output rates that step often doesn’t exist, so consistency has to be built into the tooling.
I appreciate that brand consistency sounds like a marketing preoccupation, and for a long time it was. What has changed is that the failure modes now look like IT problems. An off-brand asset is embarrassing, but an asset built on imagery the organisation never licensed is a contractual issue, and one generated by a model nobody vetted is a legal one. The people creating those assets are usually the least equipped in the business to tell the difference.
Creative Cloud for enterprise Edition 4 addresses this at the point of creation. Style Kits let branded styles and visual themes be applied consistently across teams and projects, so the standard travels with the tooling rather than living in a PDF nobody opens. Unlimited access to Adobe Stock standard assets under an extended licence removes most of the incentive to source images wherever they can be found. For IT, the outcome is fewer unmanaged asset sources entering the environment and fewer rights conversations after publication.
My first blog ended with three questions about how creative software is licensed and accessed. These two follow on from those, and they’re the ones most organisations haven’t asked yet:
Marketing and IT want the same outcome here, which is content that goes out quickly and doesn’t create exposure. We’ve simply been solving for different halves of the problem.
Adobe’s largest Australian Platinum Partner and Adobe APAC Partner of the Year. Speak to Data#3 about unlocking the full potential of Adobe Creative Cloud and Document Cloud to securely drive productivity, collaboration, innovation and digital transformation across your organisation.

Information provided within this form will be handled in accordance with our privacy statement.