NetSuite expands toolkit to ease enterprise use of third-party AI assistants with ERP data
NetSuite is expanding its AI Connector Service with what it calls Companion capabilities its customers can use to hook up AI assistants with their choice of ERP data. The update introduces prebuilt prompts, role-based controls, and domain-specific “skills” that help external AI systems better understand NetSuite’s data structures, workflows, and permissions with the help of Model Context Protocol (MCP) . Under the hood, MCP exposes NetSuite data and actions in a structured format, allowing the Companion components to broker interactions between the ERP system and external AI assistants, the company said, the company said. Companion capabilities aim to help scale AI pilots The additions could help address some of the practical hurdles that enterprise teams encounter when trying to move AI i
Could not retrieve the full article text.
Read on CIO Magazine →Sign in to highlight and annotate this article
Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
claudegeminimodel
Dying with Whimsy
To me it feels pretty emotionally clear we are nearing the end-times with AI. That in 1-4 years [1] things will be radically transformed, that at least one of the big AI labs will become autonomous research organizations working on developing the next version of their AI, perhaps with some narrow guidance of humans in oversight or acquisition of more resources until robotics is solved too. And i believe there will be some nice benefits at first with this, with the AI organizations providing many goods and services in exchange for money, to raise capital so that the self-improvement resource acquisition loop can continue. But I’m not sure how it will ultimately turn out. Declaring risk of extinction-level events less than 10% seems overconfident. Yet, declaring the risks to be >90% also see
Implementing Zero Trust Architecture for Unmanaged IoT at the Network Edge
<h2> Why Unmanaged IoT Is the Weakest Link in Your Network </h2> <p>The proliferation of Internet of Things (IoT) devices across enterprise environments has created a security paradox. Organizations deploy thousands of connected devices—IP cameras, building automation controllers, medical equipment, industrial sensors, point-of-sale terminals—to drive operational efficiency. Yet the vast majority of these devices are <strong>unmanaged</strong>: they cannot run endpoint agents, accept security patches on schedule, or participate in traditional identity frameworks. According to industry estimates, over 75% of IoT devices in production environments operate without any form of endpoint security.</p> <p>This creates a massive blind spot. Traditional perimeter-based security assumes that everyth
The Stages of AI Grief
<blockquote> <p><strong>Assumed audience:</strong> People who work with AI daily — or are starting to — and have complicated feelings about it.</p> </blockquote> <p>I don't think I've ever had so much fun in my programming career as I do now. Which is strange, because a few weeks ago I was in a very different place. I was watching - in horror - as the machine on my desk was taking over my craft. Like most people I guess, I derive quite a lot of my identity from that craft; hence the horror. (Let's ignore for now whether that's a good thing or not.)</p> <p>I just watched it melt away. Like a block of ice in the sun; inexorable. In that moment it felt like I was witnessing an emerging god: an uncontrollable force in the sky asserts its influence over all it touches, and every day, it touches
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Products
Implementing Zero Trust Architecture in IoT-Heavy Enterprise Networks
<h2> The Paradigm Shift: From Castle-and-Moat to Zero Trust Edge </h2> <p>For decades, the standard for enterprise security was the "castle-and-moat" model. This architectural philosophy assumed that anything inside the network perimeter was inherently trustworthy, while everything outside was potentially malicious. However, the explosion of the Internet of Things (IoT) and the decentralization of the workforce have rendered this model obsolete. In a modern enterprise environment, the perimeter has dissolved. Today, a smart thermostat, an industrial PLC (Programmable Logic Controller), or a VoIP phone acts as a potential gateway for sophisticated adversaries. To secure these environments, organizations must transition to <strong>Zero Trust Architecture (ZTA)</strong>.</p> <p>As defined by
Buffer Overflows on x64 Windows: A Practical Beginners Guide (Part 2): Exploitation
<h2> Introduction </h2> <p>Welcome back. Mirrai here. In part 1 we covered the theory. The stack, RIP, and what a buffer overflow actually is. Now we get our hands dirty. By the end of this guide you should have a working exploit that gives you control of RIP and redirects execution to your own code.<br> Before we start, make sure you have x64dbg and pwntools installed from part 1. You'll also need the vulnerable program we wrote. If you haven't read part 1, go do that first. Buckle up, this might take a while.</p> <p>For your convenience, here's the old vuln program code<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight c"><code><span class="cp">#include</span> <span class="cpf"><stdio.h></span><span class="cp"> #include</span> <span class="cpf"><windows.h></span><s
DeepSource for Python: Static Analysis and Autofix
<p><strong>DeepSource provides one of the most thorough Python static analysis experiences available in 2026.</strong> Its Python analyzer covers over 150 rules across bug detection, security scanning, performance optimization, and code style enforcement - with a sub-5% false positive rate that keeps findings actionable rather than noisy. Combined with Autofix, which generates ready-to-apply code changes for detected issues, DeepSource turns Python static analysis from a reporting exercise into an automated remediation workflow.</p> <p>This guide covers everything you need to set up DeepSource for Python projects - from the initial <code>.deepsource.toml</code> configuration to advanced features like type checking integration, Django and Flask security rules, and coverage reporting with py
How I built an AI that reads bank contracts the way bankers do (not the way customers do)
<h1> How I built an AI that reads bank contracts the way bankers do (not the way customers do) </h1> <p>The problem started in 2009. I was a banker. I watched loan officers use internal scoring grids that customers never saw. The information asymmetry wasn't illegal — it was just never shared.</p> <p>Fifteen years later, the asymmetry got worse. Banks now run LLMs on customer data before any human reviews it. The customer still signs without understanding what they're signing.</p> <p>So I built the reverse.</p> <h2> The core insight: bankers read contracts differently than customers </h2> <p>A customer reads a loan contract linearly — page by page, looking for the monthly payment.</p> <p>A banker reads it dimensionally — simultaneously scanning for:</p> <ul> <li> <strong>Covenant triggers<
Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!