Italy just billed Meta €805 million for a Facebook Android feature that treated the camera roll as inventory.
The Garante found the app could read photos, videos, and related metadata on Italian phones without explicit consent, and that the post-from-gallery helper was on by default. That’s a cybersecurity failure dressed as convenience. You already run the same pattern in the fleet. A permission nobody reviewed. A media store your firewall never inspects, because the read happens on the handset, not across a perimeter you instrumented.
Italy gave Meta 60 days to act. Your incident response clock starts the moment a work photo lands in a consumer gallery with a default-on uploader sitting on top of it.
Default Grants Undo Your Cybersecurity Stack
Defense in depth that stops at the network edge is a comfort story. Gallery access, document providers, and backup syncs live below that edge. Threat detection tuned for inbound brute-force noise won’t flag a social app reading DCIM because the OS said yes once, months ago, during setup.
Threat-protection catalogs are even worse at this. They score malware families. They rarely score a legitimate client that ships a default media crawler and calls it a posting assistant.

Work phones and BYOD handsets are full of those assistants. Screenshots of tickets. Photos of whiteboards. PDFs of invoices saved to Downloads. If Facebook can suggest them, so can every other app you approved because someone in the business wanted a chat bubble.
You asked users to be careful. The app never asked them anything that counted.
Your cyber security program still treats this as a privacy complaint.
Treat it as standing access. The Garante’s point is operational even if you never touch Meta. Explicit consent is the human-readable version of least privilege. Default-on is standing admin on a data store you don’t inventory.
Security hardening that only patches the OS and leaves photo, file, and backup scopes wide open is unfinished work.
Renaming Intelligence Will Not Shrink Scope
While Italy priced a default toggle, the Pentagon renamed the Chief Digital and Artificial Intelligence Office the Super Intelligence Office. The move follows a presidential order to swap “artificial intelligence” for “super intelligence” in executive branch communications.

The rename doesn’t change a single ACL.
You’ll see the same reflex inside companies. Rebrand the AI steering group. Publish a responsible-use page. Leave the mobile permission matrix untouched. Super intelligence, generative assistants, posting helpers: the control is which local stores the binary can open without a prompt you can prove.
This is a bad look for any shop that spent 2026 talking model governance while consumer apps on corporate devices kept a live pipe into photos and files. If your board packet has an AI risk slide and no mobile media-scope inventory, you’re doing the Pentagon maneuver. New name. Same grant.
Operators who wait for Washington to define the term will still have phones that can read every badge photo taken at the all-hands.
Language is cheap. Scope is the bill.
Lock Media Access Like Privileged Scope
You can cut this risk without waiting for the next regulator. Do it in two passes: what you can kill this week, and what you keep doing every quarter.
Start here this week.
- Export the live permission matrix from MDM and identity: photos, files, contacts, microphone, backup. Revoke default media access for any app that is not a camera or a managed file client.
- Split work profiles from personal galleries. If you can’t split them, treat BYOD photo access as an unmonitored share to every social and assistant app on the device.
- Hunt for default-on “suggestion,” “memories,” and “smart upload” features in sanctioned collaboration and social clients. Disable them at the app-config layer so they survive the next install.
- Pull last 90 days of DLP and CASB hits for image and video uploads from mobile. If you have none, your telemetry is blind.
Ongoing work is dull and it’s the job. Recertify media scopes the way you recertify privileged groups. Add permission diffs to threat-protection reviews so a newly defaulted feature shows up as a change in your queue, before a regulator writes the blog post. Put gallery and files access into tabletop incident response so the first question is which apps could read the roll. Copying a firewall rule comes later, if it ever matters.
Build an allowlist with teeth. Camera apps get the camera. File clients get Documents. Everything else gets a denial that survives reinstall.
Keep the personal identity off the work profile. SSO into a consumer social app from a managed account is how a gallery scrape becomes a company record in someone else’s cloud.
If legal owns consent language and security owns malware, the default toggle sits in the gap. Close the gap by making app-config and permission recert a change-control item with an owner, a ticket, and a rollback.
None of this requires a new platform. It requires you to treat local media like a file share with world-readable ACLs, then fix the ACLs.
Meta can write a check. You still have the same default sitting on the devices you issued. Price it before Italy prices it for you.
Sources
- Italy Fines Meta €805 Million Over Facebook’s Android Gallery Access Without Explicit Consent
- Pentagon Renames CDAO ‘Super Intelligence Office’
Take Control of Your Server Security
Don't let brute-force attacks slow you down. Try IPBan Pro risk-free for 30 days.
Secure. Automated. Lightweight.
Take Control of Your Server Security
Don't let brute-force attacks slow you down. Try IPBan Pro risk-free for 30 days.
Secure. Automated. Lightweight.
