510 press releases in English indexed under cybersecurity.
Organizations can adopt AI-driven security operations solutions to help protect against cyber threats SAN JOSE, Calif., October 20, 2026--Stellar Cyber, a leading provider of security operations solutions and an Oracle partner, today announced that Stellar Cyber Security Operations Platform , Stellar C
Legacy-to-cloud modernization cuts costs, while bundled managed services secure recurring revenue; AI, cybersecurity and edge analytics unlock cross-sell opportunities. Legacy-to-cloud modernization cuts costs, while bundled managed services secure recurring revenue; AI, cybersecurity and edge analytics unlock cross-sell opportunities.
Schneider Electric reveals water is now one of the biggest risks to industrial business, ranking as highly as cyber-attacks & supply chain disruption
LOS ANGELES, October 20, 2026--Resecurity ® , a global cybersecurity and threat intelligence company trusted by Fortune 100 enterprises and government agencies, will exhibit at The Special Operations Forces Exhibition and Conference ( SOFEX 2026 ), taking place October 27-29, 2026, at the Aqaba Intern
Support from EDB and EDBI to facilitate regional growth and continuous, evidence‑based cyber resilience SINGAPORE, October 20, 2026--Please replace the release dated October 18, 2026, with the following corrected version due to multiple revisions. The updated release reads: HORIZON3 EXPANDS IN SINGAPOR
In recent trading sessions, several technology stocks, including Wix, UiPath, SentinelOne, Amplitude, and Commvault, saw significant declines. This downturn is attributed to a shift in investor focus from the potential of artificial intelligence (AI) technology to concerns about how companies will finance these advancements. The financial markets are reacting to these concerns, which are compounded … Continue reading "Tech Stocks Decline Amid AI Funding Concerns"
In the latest trading session, SentinelOne (NYSE:S) experienced a notable decline in its stock price, closing at $21.58. This represents a significant drop of 7.68% from the previous day. The decline in SentinelOne’s stock was more pronounced than the broader market, with the S&P 500 index experiencing a loss of 1.09%. Meanwhile, the Dow Jones … Continue reading "SentinelOne Shares Drop Sharply, Outpacing Market Losses"
AI coding agents are writing and changing code, from GitLab Duo Agent Platform agents to externally connected agents like Claude Code, Cursor, and Codex. You are accountable for what those agents do, yet most of their activity stays invisible: which agents ran, who used them, and what they touched. Teams often struggle with understanding whether a developer used a tool or model that is approved or not. The AI Governance Dashboard, now in beta, gives you one place to see agent activity across your top-level group. It brings GitLab Duo Agent Platform agents and the external agents your developers connect into one view, showing which agents ran, who used them, and which projects they touched. The dashboard also shows the tools and sessions associated with each agent. With that audit trail in place, you can answer the questions auditors and risk owners ask: who ran this agent, what did it do, and who is accountable for it. Every agent action gets recorded in one audit trail, detailing the model it used, the tools it called, and the project it ran in. You can now investigate a session or hand an auditor evidence without stitching together multiple sources of data. Watch a demo of the AI Governance Dashboard: Gain visibility into AI agent activity More AI agents are running across your organization than you can track by hand. GitLab Duo Agent Platform agents run inside GitLab, while externally connected agents like Claude Code, Cursor, and Codex run on developers' own machines. The result is the shadow AI problem: real work happening in your projects, from many tools, that no one accountable can see in one place or tie to a team member. The AI Governance Dashboard brings that activity into view and connects each agent to the developer behind it. To turn it on in your top-level group, go to AI > Governance. GitLab Duo Agent Platform agents and externally connected agents appear together, and you can toggle between the views to see all agents, just Duo Agent Platform Agents or just externally connected agents. Three tiles at the top give you a baseline: how many agents ran, how many sessions they started, and how many tool calls they made over the past seven or 30 days. Each tile shows the daily trend and the change from the previous period, so a spike, like a new tool your team started using last week, stands out. The cards below tell you where to act. You can check whether the agents your developers rely on match the ones you approved, see which projects carry the most agent activity and need closer review, and know who to talk to when usage shifts. Prove what every agent did Managing AI risk starts with knowing what every agent did and who prompted it. Traditional audit trails were built for human changes, so that record is often scattered across tools or missing. GitLab records every agent action as an audit event, so you can investigate an incident or answer an auditor from one place. Open any GitLab Duo Agent Platform session to see the prompt the developer sent, the tools the agent called, the MCP servers it used, the model that ran, and the project it changed. From there, you can download an immutable copy of the session as evidence, or stream the events to your security information and event management (SIEM) system. Set up your dashboard today It only takes a few steps to set up the AI Governance Dashboard: Check access. The dashboard needs the Owner role on the top-level group, or a custom role with the read_agent_artifacts ability. If the people who should watch agent activity don’t have Owner access, create that custom role first. Turn on AI audit event storage. Storage is off by default, and events are only recorded after you turn it on. In your top-level group, go to Settings > GitLab Duo, select Change configuration, and then Store AI audit events in the Data and privacy section. You need to have an Owner or Security Manager role to have access. Open the dashboard. In your top-level group, go to AI > Governance, and select the Dashboard tab to see your GitLab Duo Agent Platform activity. Connect your externally connected agents. Sign in with GitLab CLI (glab) 1.122.0 or later on macOS or Linux. To capture Claude Code sessions, run glab govern setup, which installs the Claude Code hooks. To also capture Cursor and Codex sessions, run glab govern setup --agents codex,cursor, which adds a background job that sends those sessions every 30 minutes. Run glab govern doctor to confirm the setup works. The AI Governance Dashboard is in beta for GitLab Premium and Ultimate customers. Turn it on for your top-level group to keep oversight of AI usage as fast as your teams adopt it. Not on GitLab yet? Try GitLab Ultimate for free and use the AI Governance Dashboard to get started.
Broken object-level authorization ranks first on the OWASP API Security Top 10, and OWASP says that traditional static application security testing (SAST) tools struggle to find access control flaws. A missing authorization check is an absence of code, so a scanner that matches patterns has nothing to match. You can find the gap only if you already know what the endpoint is meant to enforce. We're building Business Logic Security Analyzer in GitLab Duo Agent Platform to catch business logic vulnerabilities that pattern-based scanners miss. It is now in early access for GitLab Ultimate customers on GitLab.com. Valid code, wrong intent Any application security team will recognize these three findings: An endpoint takes an order ID from the request and returns the order without checking who owns it. A role field on a user profile accepts whatever JSON the client sends. A user ID is a sequential integer. Each one is valid code that slips past most taint and pattern rules in a conventional SAST engine, because no untrusted data reaches a dangerous sink, and no known-bad signature appears. Chained together, they hand an attacker every customer's order and an administrator role. Across GitLab's customer base, codebase size has grown as much as 500% as agents write code. CVE disclosures through April ran 46% above the February forecast from the Forum of Incident Response and Security Teams. The same AI models that generate code also make existing weaknesses less expensive to discover and chain. Authorization logic is where that pressure lands: Developers and agents write a check in a line or two, but when one is missing, the gap often goes unnoticed. As Omer Azaria, vice president of Product Management at GitLab, put it at GitLab Transcend, "We're caught in the middle: more code, faster attacks, same teams." Why whole-repository scanning starts here GitLab Duo Security Review looks for authorization flaws in merge requests, but many business logic flaws aren't visible in a diff. Whether an endpoint should check ownership depends on the data model, the roles the application defines, and how other endpoints treat the same records. Judging one handler means reading the application around it. That is why Business Logic Security Analyzer scans the whole repository, and why GitLab is the platform to do it on. The source code, the pipelines that build it, the security findings attached to it, and the policies that gate it all live in one system. An agent that scans here sees the full application and writes its findings where the security team already works. At Transcend, we introduced the GitLab Security Standard: five stages each agent must clear to earn more autonomy, built on the premise that code is now abundant and trust is scarce. Its Verify stage requires every change, whether written by a person or agent, to pass controls the author cannot touch. Business Logic Security Analyzer runs outside the author's hands, and its findings persist in the same report and dashboards that govern the rest of the codebase. How the analyzer works Business Logic Security Analyzer is a foundational flow on GitLab Duo Agent Platform that targets business logic flaws, starting with broken object-level authorization, missing or improper authorization, and mass assignment. A practitioner can run a whole-repository scan, and scan each merge request automatically after its pipeline passes. Detecting any of these flaws requires a model of what the application is meant to do. Pattern scanners have none, but an agent that reads the repository can build one. The analyzer starts by enumerating the application’s entry points and mapping who should be allowed to do what: which records belong to which user, and which actions are administrative. It then reads each handler in scope and checks whether the handler enforces that rule before touching the record. Findings land in the Vulnerability Report and the merge request security widget as first-class SAST results, to support triage, remediation, and auditing. In the demo application below, refund_order accepts an order_id from the request and sets refunded=1 without checking that the caller owns the order or is an administrator. Taint rules stay silent because the query is parameterized. The analyzer reports it as CWE-639, Critical, at app/orders.py:17, and its explanation names the missing ownership check. The models behind the analyzer Business Logic Security Analyzer is the first GitLab capability supporting Anthropic's Claude Mythos 5.1, and is available in early access to customers in approved environments. The model sees only GitLab's prompts and the customer's repository, which holds the context the analyzer needs: the data model, roles, and rules each endpoint enforces. As Rajat Pandit, Head of Applied AI, Anthropic India, said at Transcend, "When defenders have more context than attackers, advanced models change the math in their favor." Alongside Mythos, the analyzer supports Anthropic’s Claude Opus 5.5, Sonnet 5.5, Sonnet 5, and Sonnet 4.6, with more models planned for future releases. All of them run as GitLab-managed models through GitLab’s AI gateway, under the same data handling terms as the rest of GitLab Duo Agent Platform. Request early access Business Logic Security Analyzer is in early access for a small group of GitLab Ultimate customers on GitLab.com. Participants run the analyzer on their codebases to find true positives their security teams didn’t already know about. We will work with each team to learn where the analyzer is correct, wrong, or silent. Each scan consumes GitLab Credits, and cost scales with the size of the application's attack surface. To be considered, contact your account team, or, if you are not yet a GitLab customer, contact our sales team. Once your group is enabled, start a whole-repository scan from GitLab Duo Chat or through the API, and attach the Business Logic scan profile to a project to scan its merge requests. The Business Logic Security Analyzer documentation covers prerequisites and setup.
Veteran technology executive will lead Alaska’s enterprise technology, data, digital, cybersecurity and AI strategy, focused on operational reliability, modernization and long-term growth Siva brings nearly three decades of technology leadership experience across CVS Health, Target Corporation and GE Capital, including large-scale cloud, digital, data and AI transformation SEATTLE, Oct. 19, 2026 — Alaska Airlines, … Continue reading "Alaska Airlines names Amaresh Siva Chief Information Technology Officer"
Senior Advisor, Go-to-Market appointment brings global cybersecurity experience to enterprise buying decisions [PR.com]
Scott F. Gelbard, Founder of SGI Global Partners Inc. and Managing Partner of Peak Ventures, today announced a 2027 thought leadership initiative expanding his International Business Series into five new subject areas critical to mid-market business owners and family office executives. The new initiative builds on the success of Gelbard's International Business Series, which has produced more than 100 published artic