
SAP puts its agent containment work into OpenShell
SAP's four contributions to the OpenShell agent runtime are containment and operability engineering, and the runtime is free only through October.
Topic coverage
Source-linked reporting and practical patterns organized around a shared enterprise applications question.

SAP's four contributions to the OpenShell agent runtime are containment and operability engineering, and the runtime is free only through October.

Microsoft now hosts Copilot-generated code inside the tenant boundary, and the admin center inventory matters more than the hosting does.

An Oracle press release pairs undated patient intake with prescriber credentialing that ships now. The reusable credential model is the part worth copying.

An ODP security check has landed in SAP EarlyWatch Alert, putting a June note about unchecked RFC callers in front of people who never read the patch queue.

Most of ServiceNow's Brazil deprecation list is a planning signal. One line is a live change to how catalog role ACL grants work on upgrade.

Microsoft's Dynamics 365 ERP MCP server is generally available, while the role-based access controls written for agent use are still described as coming.

Microsoft's updated Power Platform bounty schedule pays double for critical cross-tenant flaws and names Dataverse twice. Here is what an admin should check.

Microsoft now provisions and renews SSL and TLS certificates for Power Pages custom domains, but the option does not appear when CDN or WAF is enabled.

ServiceNow's new agent kill switch orchestrates credential revocation across Okta, GCP and AWS. What the post does not say matters more.

Salesforce says TSA's Ace agent resolves 96% of roughly 100,000 monthly traveler conversations without escalation. That rate deserves a second look.

Three quarters of CIOs told diginomica they can't see every AI tool in their systems. ServiceNow's shift zero pitch depends on data they don't have.

ServiceNow will run Experian's risk and identity agents on live loan and claims decisions, but Experian built and controls them.

Siebel CRM took 63 patches in Oracle's latest Critical Patch Update, a sign the platform isn't as dead as budget plans assume.

Salesforce put a number on Claudeforce at Dreamforce 2026, 37 sales skills running through an MCP server in Claude, and that number is a permissions question first.

The autonomous security specialists ServiceNow previewed in June reach general availability today, and the checklist for trusting them is still thin.

Oracle September update shipped 673 patches, but the number that matters is how many are reachable without a login, and Oracle already named where that risk concentrates.

Oracle's September update fixed 240-plus flaws needing no login at all. That says less about Oracle's code than what stays reachable from the open internet.

ServiceNow's MCP servers keep ACL and role enforcement in place, so what an agent can do is decided by the role model your instance already has.

Salesforce's six-part enterprise AI model lists Trusted Context first. Our read: what an agent can see and understand is the limit of what it may do.

ServiceNow's AI Gateway enforces policy as an agent invokes an MCP tool. Here is which rules belong at that layer and which still belong to the record.

Salesforce's AI Control Plane will observe agent behaviour and outcomes. Explaining a single action needs a per-call record the post never describes.

Salesforce in Claude ships 37 prebuilt sales skills. Each one encodes a definition of deal health and pipeline review that your org may not share.

Salesforce says an admin connects Salesforce in Claude once and permissions are managed centrally. Whose identity each action runs under is the question to ask.

Salesforce in Claude reads CRM and Slack data through one admin connection. Governing the writes, where business rules and side effects live, is the hard part.

Salesforce says Claudeforce routes actions through its rules. Here is what the trust boundary must still carry when a seller never opens Salesforce.

Salesforce says Claudeforce moves from select pilots to open beta in September 2026. What a Salesforce team should settle before sellers connect Claude to CRM.

Salesforce sharing only ever adds access, and the platform stores the result. How to set the baseline, the hierarchy and the rules so growth stays affordable.

Business units, depth, teams and sharing decide whether a Dataverse security model survives growth. How to design each one so it still makes sense later.

An assistant grounded in SAP data is only safe if it inherits the authorisation check rather than retrieving broadly and filtering the results afterwards.

Provisioning is the easy part. Transfers add access and almost never remove it, and every application keeps entitlement in a model of its own.

A Power Pages site authenticates against an identity provider and authorises against a Dataverse contact. Matching the two on email is the mistake that lasts.

Integration accounts miss every joiner and leaver process. Give each one a named owner, a readable name, narrow scopes and a rehearsed rotation.

When a company runs more than one Salesforce org, single sign on is the easy part. The gap audits find sits in deprovisioning across two login domains.

When ITSM and security both claim the CMDB, reconciliation becomes everyone's second job, and nobody notices a stale record until a remediation deadline depends on it.

Access exceptions in Dataverse and ServiceNow outlive their reason. Give each one a named owner, an end date, and a record small enough to review.

A pause control with an owner, a written reason, and a resume record should be an ordinary operating control for Copilot Studio and ServiceNow agents.

Content assignment decides what a user sees, authorisation decides what runs, and the two drift apart unless you design roles around the job.

Function access decides what someone can do. The security profile decides whose records they do it to. Most Fusion HCM exposures live in that gap.

A permission role says what may be done and a group says who does it. The assignment binds granters to a target population, and that pairing is where access breaks.

A Power BI import carries everything the refresh account could read. Rebuild the row filters, maintain the mapping table, and test as a restricted user.

A table permission granted for one page applies everywhere that table can be reached. Check the whole surface before a Power Pages site faces the internet.

When finance is too small to split creating a vendor from paying one, pick the two conflicts that carry the money and mitigate them in writing.

A working method for auditing Salesforce profiles and permission sets, and removing the access you find without breaking someone's Monday.

Oracle and SAP both ship bundles where nearly every entry claims top severity. Here is the four-question order I actually use to triage them for real.

Before a Copilot Studio or Agentforce pilot gets more users, check it has four named owners, a visible failure path, and a review date.