Products & Tools

Opsera expands Forge for governed legacy modernization

Opsera's expanded Forge maps legacy dependencies, grades security risk through a NIST-aligned scorecard and adds approval gates for AI-assisted modernization work.

Opsera Expands Forge With Security and Governance for Legacy Application Modernization
Opsera Expands Forge With Security and Governance for Legacy Application ModernizationBoskampi / pixabay
By James Calloway6 min read

Why it matters

  • Forge's update groups its capabilities into four connected areas: application discovery, security intelligence, ForgeScore assessments and pipeline controls.
  • ForgeScore uses eight dimensions and A–F grades, but NIST does not certify or endorse the assessment mechanism.
  • Forge connects with more than 150 development, security and delivery tools.
  • In June, Anthropic said partners using Claude Mythos Preview had found more than 10,000 high- or critical-severity flaws.
  • The NIST Cybersecurity Framework organizes outcomes around six functions: Govern, Identify, Protect, Detect, Respond and Recover.

By James Calloway

Opsera's expanded Forge adds four connected controls—application discovery, security intelligence, ForgeScore assessments and pipeline controls—for AI-assisted modernization of legacy software (older systems carrying accumulated business and integration dependencies). Opsera frames the release around a specific enterprise risk: AI can generate code faster than engineers can map years of business rules, integrations and operational assumptions embedded in an application.

Replacing a component without that context can turn a security repair into a production problem, according to Opsera. The company says Forge customers can use the capabilities now, giving engineering, product and security teams a shared view of application risk as modernization proceeds.

The announcement gives no customer count, measured risk reduction or independent validation for the new controls. Its case therefore rests on workflow design rather than published outcome data.

What does Opsera's expansion change?

Opsera divides the update into four connected areas and extends its earlier checks for vulnerabilities and exposed credentials:

  • Application discovery: Forge maps business rules and dependencies, helping teams choose which systems to modernize first and assess a change's impact.
  • Security intelligence: Built-in checks flag known vulnerabilities, exposed credentials and outdated components, with explanations intended to connect technical findings to business risk.
  • ForgeScore assessments: An eight-dimension scorecard expands support for the NIST Cybersecurity Framework and assigns A–F grades to communicate modernization and security risk to leadership.
  • Pipeline controls: Administrators can set stages, approvals and goal scope so AI-assisted work stays within agreed requirements and priorities.

Opsera also describes impact analysis for upgrades, which identifies affected applications before a change ships. The company says this links discovery and security: an outdated dependency matters more when engineers can see what relies on it and plan the replacement.

Takeaway: Forge offers a more controlled path for AI-assisted modernization, but the announcement has not shown that the controls reduce production risk.

How does Forge control AI-assisted coding?

Opsera's documentation describes a living knowledge graph, a mapped network of relationships among code, business rules, dependencies, data and policy. The graph aims to give engineers and coding agents (AI systems that carry out software tasks) reusable context instead of forcing every task to reconstruct it.

That context feeds versioned specifications and work orders covering requirements, tests, architecture and completion criteria. Before code generation, Forge applies policy and security checks, then requires human approval for merges and links each change to its requirements and test evidence.

Opsera says Forge works with models and assistants including Anthropic, OpenAI, GitHub Copilot and Cursor, and connects with more than 150 development, security and delivery tools. In that arrangement, the agent operates inside a managed system that supplies context and controls how work advances, rather than acting as a standalone code generator.

“Frontier AI has made finding vulnerabilities easier. Fixing them inside legacy code nobody understands is still expensive,” said Vishnu Vasudevan, Chief Product Officer of Opsera. “With the Forge Software Factory acting as the AI harness around the models and agents teams already use, every modernization project becomes a security remediation project, and leadership gets a NIST-aligned grade they can take to the board.”

The announcement does not explain how often the graph refreshes, how its accuracy is measured or what happens when its context conflicts with an agent's proposal. It also gives no measured gains in delivery speed, defect reduction or review time for the expanded workflow.

Takeaway: Forge's main promise is control, but the announcement supplies architecture instead of measured results.

What do the ForgeScore grades measure?

Opsera describes ForgeScore as a baseline for comparing an application's condition before and after modernization work. Its dimensions include changing tightly coupled systems (dependent components), protecting trust boundaries (access-control boundaries), production resilience (operational stability), business-logic clarity and readiness for future architectural changes.

The company says expanded NIST alignment gives leaders a common risk-management vocabulary. The NIST Cybersecurity Framework (CSF), a risk-management structure, organizes outcomes around six functions: Govern, Identify, Protect, Detect, Respond and Recover.

Forge's letter grades provide Opsera's assessment mechanism; NIST does not certify or endorse CSF-related products or implementations. That distinction matters because “NIST-aligned” describes a design relationship, not an external validation mark.

Opsera says a system can compile and run on a newer platform while remaining difficult to understand, risky to change or dependent on fragile interfaces. The scorecard measures those modernization conditions rather than merely whether the software starts.

The announcement does not publish the scoring formula, dimension weights, A–F cutoffs or an independent validation of the grading. Nor does it provide before-and-after results from named customers.

Takeaway: ForgeScore may make inherited risk legible to executives, but its grades remain Opsera's judgment until it shows how it calibrates them.

Why is finding flaws only the first step?

Opsera's release arrives as AI-assisted vulnerability discovery increases the volume of issues defenders can identify. In a June update on Project Glasswing, Anthropic said partners using Claude Mythos Preview had found more than 10,000 high- or critical-severity flaws.

Anthropic also identified verification, disclosure and patching as a growing bottleneck. That context supports the emphasis on application knowledge, but it does not prove Forge can shorten the remediation cycle.

Opsera describes a useful sequence: establish which systems an issue affects, preserve required behavior, validate the fix and route it through the organization's approval process. Finding the flaw covers only one part of that work.

For example, upgrading a shared runtime (a software layer used by several applications) can affect multiple applications and integrations at once. Opsera says a dependency map can set test scope, specifications can record behavior that must remain intact, and approval gates can give reviewers evidence before deployment.

The announcement does not connect Anthropic's Glasswing findings to Forge deployments, and Opsera supplies no customer metrics for remediation time or production failures. That leaves the strongest external figure in the announcement as industry context rather than product validation.

Takeaway: Finding flaws is becoming easier; safely changing old systems still depends on evidence Opsera has not quantified.

How does modernization connect to AI spending?

Forge sits alongside Opsera's Unified Insights platform, which connects AI usage and cost with engineering delivery. Opsera describes spending views by model, tool and team, plus measures of how work moves from commits through review and production.

The company argues that more generated code or greater agent use does not by itself show an application became safer or easier to maintain. Instead, it points to before-and-after assessment, traceable change history and delivery data as stronger evidence of improvement.

Forge's expansion applies that test to modernization by asking what the application does, where inherited risks sit and what evidence supports each change. The announcement does not disclose a rollout schedule, named customer results or measured savings in AI spending. It also supplies no before-and-after scores, traceable change histories or delivery measurements for the new modernization workflow.

Those records would test whether a NIST-aligned grade reflects real risk reduction or only a clearer presentation of the work.

Takeaway: Forge's next test is not more generated code, but published before-and-after evidence that governed modernization reaches production with fewer inherited risks.

Source: unite.ai

Share this article:

More from James Calloway

James Calloway

Show full bio

News editor covering people, launches and day-to-day practice in artificial intelligence and machine learning at AI In Context.

722 articles

Related articles

  1. Novee adds external attack surface testing to its AI pentesting platform
  2. Commvault and Zscaler Team Up to Govern and Recover Enterprise AI Agents
  3. Onyx and Glean integrate controls for enterprise AI agents
  4. OpenAI and Hugging Face reveal findings from model evaluation security incident
  5. OpenAI says Astra hits critical cyber capability threshold

« Previous articleNext article »