Author: Mike Vizard

  • Survey: Pace of Increased Adoption of GitOps Varies Widely

    Survey: Pace of Increased Adoption of GitOps Varies Widely

    A survey of 660 software development professionals finds 93% have embraced GitOps as a methodology for building and deploying software, with 68% planning to increase usage.

    Conducted by Octopus Deploy, a provider of an automation platform for releasing software, the survey finds another quarter (25%) plan to retain their current usage compared to 7% that plan to reduce or stop GitOps usage.

    Steve Fenton, director of developer relations for Octopus Deploy, said the survey also makes it clear that GitOps maturity levels also tend to vary considerably. For example, under one-third of organizations use GitOps across less than 20% of their production systems. The survey also finds only 35% of respondents that have adopted GitOps make use of continuous reconciliation and automatic rollback mechanisms. That suggests that many organizations might only be going so far as to house infrastructure-as-code (IaC) configurations alongside source within a centralized Git repository.

    GitOps, at its core, refers to the process of automating the provisioning and management of IT infrastructure using a set of best practices that extend to include IaC tools. Ideally, a GitOps workflow should ensure a system is managed declaratively, automatically pulls the desired state declarations from the source, stores that data in a way that enforces immutability and versioning, and then provides some way to observe those interactions.

    Once infrastructure is managed with code, it becomes easier to converge the management of IT operations and application deployment. Kubernetes, meanwhile, provides an ideal GitOps platform because it presents a standard set of application programming interfaces (APIs) that enable clusters to automatically pull code as required versus requiring an IT team to manually push code out to a platform.

    Regardless of the level of GitOps maturity, there tends to be a high correlation between adoption of GitOps and modern IT platforms such as Kubernetes, noted Fenton. In general, many organizations are typically inclined to rethink legacy processes whenever a new platform is adopted, he added. In fact, it’s not uncommon for a team that has adopted GitOps to deploy microservices-based applications to be working along software engineering teams that are using legacy approaches to deploy more monolithic applications, said Fenton.

    A GitOps workflow should ultimately make it simpler for IT operations to achieve continuous delivery of applications, a goal that has remained elusive despite the widespread deployment of continuous integration/continuous delivery (CI/CD) platforms. In fact, while CI is widely used to build applications, the percentage of organizations consistently using CD to deploy software has remained comparatively small.

    It’s not clear to what degree the rise of platform engineering as a methodology for managing DevOps workflows at scale might drive increased adoption of GitOps. The one thing that is certain is that as the pace of application development continues to accelerate in the age of artificial intelligence (AI), the need to revisit software engineering workflows will become apparent. The only issue to be resolved now is determining how much to revamp existing workflows versus opting to simply start over again from scratch.

  • Kusari Adds AI Security Tool to Inspect Code as Pull Requests Are Made

    Kusari Adds AI Security Tool to Inspect Code as Pull Requests Are Made

    Kusari has added an artificial intelligence (AI) tool that runs a security risk assessment every time an application developer makes a pull request.

    Company CTO Mike Lieberman said Kusari Inspector is designed to make it simpler for security to be shifted left toward application developers in a way that doesn’t impinge productivity.

    Most application developers care about security, but getting the information they need to ensure it has historically been problematic, said Lieberman. Kusari Inspector makes use of AI and dependency graph analytics to surface issues long before vulnerabilities and other structural flaws are incorporated into a software build, he said.

    Using a tool priced at $10 per seat per month, Kusari Inspector continuously learns about the codebase and individual application developer preferences, making it possible to generate instant, context-rich, annotated security reports with inline explanations for every new or updated pull request. Developers are then provided go/no-go guidance, remediation suggestions, and step-by-step instructions to mitigate risks such as exposed credentials, misconfigurations, typosquatted or maliciously named dependencies and prohibited licenses.

    In addition to identifying those issues, Kusari Inspector will also rank risky, low-trust, or vulnerable dependencies—direct and transitive—based on multiple data sources to provide developers with a deeper understanding of application security issues, said Lieberman. Developers via a natural language interface can also chat with Kusari Inspector to clarify findings, customize recommendations, and set security standards.

    Finally, Kusari Inspector will automatically generate and collect source data for a software bill of materials (SBOM) across all connected projects and repositories.

    The core Kusari platform leverages AI to identify dependencies and understand the blast radius of incidents using metadata it collects from throughout the software supply chain. That capability is now being extended further left to provide application developers with a tool that enables them to write more secure code.

    It’s not clear how much DevOps teams are investing in AI, but a recent Futurum Group survey finds that 41% of DevOps professionals expect generative AI tools and platforms will be used to generate, review and test code. A separate Futurum survey of cybersecurity leaders finds all are investing in software supply chain security, with application security posture management (ASPM) and DevSecOps automation and orchestration topping the priority list, followed closely by security composition analysis (SCA) tools, application programming interface (API) security and dynamic application security testing (DAST) tools. In addition, 30% of respondents expect to be piloting a software bill of materials (SBOM) initiative in the next 24 months/

    However, the source of the funding for these initiatives is becoming more of a shared responsibility, with only 21% of respondents reporting that security budgets are the sole source. In fact, half of the respondents (50%) noted that application development teams now own responsibility for application security.

    Overall, only 25% of respondents said there is limited collaboration with application development teams, resulting in occasional friction, compared to 59% that said there is good collaboration with room for improvement. Only 16% said there is a tight partnership based on shared goals.

    Hopefully, AI tools will continue to close that gap in a way that reduces the current level of stress felt today by all concerned.

  • Fast Code, Real Risks: Guardrails for AI-Generated Software

    Fast Code, Real Risks: Guardrails for AI-Generated Software

    Yonatan Arbel, developer advocate in the Office of the CTO at JFrog, dives into the potential risks and rewards of relying on artificial intelligence (AI) agents to build and deploy software.

    Yes, more code is shipping faster than ever, Arbel admits, but volume alone isn’t a win—each hastily synthesized line must still survive build servers, security scanners and production reality. “Not everything in life comes for free,” he reminds, framing AI acceleration as an IOU that must eventually be paid down with careful review.

    To drive the point home, Arbel shares a personal misadventure. While traveling, he used a “vibe-coding” platform to whip together a receipt-tracking app. The tool auto-generated an impressive login flow and slick UI, so he proudly shared the URL with friends—only to discover their receipts mixed with his the next morning. A quick code dive revealed an AI-written SQL query that fetched every user’s data instead of scoping to the current account, proving how easily privacy can be breached when humans skip the boring inspection step.

    From there, the conversation turns to guardrails. Developers are becoming “pilots with copilots,” Arbel notes, spending more time instructing chat windows than writing functions. That shift demands automated policy checks, dependency vetting and runtime governance so velocity doesn’t eclipse trustworthiness. DevOps teams must embed quality gates early and often, treating AI-generated packages and prompts just like any other third-party code subject to organizational rules.

    Arbel’s advice is pragmatic: Start small, review everything, and remember that speed without oversight is just a fast track to technical—and financial—pain. Used thoughtfully, AI can compress months of work into days, but only if teams stay vigilant, enforce context-aware policies and let security evolve in lockstep with the bots.

  • Spacelift Adds On-Premises Edition of Infrastructure Management Platform

    Spacelift Adds On-Premises Edition of Infrastructure Management Platform

    Spacelift has made available an on-premises edition of a platform for automating the provisioning and management of IT infrastructure that previously was only accessible via a software-as-a-service application.

    Company CEO Pawel Hytry said the on-premises edition of the platform satisfies both the requirements of highly regulated industries and the emergence of sovereign cloud requirements that stipulate data must remain within a specific geographic region.

    Regardless of whether this edition of Spacelift is deployed in a local data center or in a cloud service that ensures IT infrastructure is restricted to a single availability zone, the Spacelift observability platform can now be deployed in a way that satisfies any compliance requirement, he added.

    It’s not clear how many organizations that previously relied on a SaaS edition of the platform might be required to shift toward an on-premises edition because of sovereign cloud requirements that have risen in the wake of recent globe trade tensions. Organizations in Europe have now become especially sensitive to dependence on IT infrastructure that might reside in the U.S. out of fear that the U.S. government might impose additional restrictions in the form of, for example, a tariff on digital services.

    It’s also unclear how many providers of SaaS platforms might need to address similar sovereign cloud requirements, but it’s evident IT teams will soon have a lot more deployment options to consider.

    In the meantime, Spacelift is making a case for a platform that makes it easier to enforce best practices across the infrastructure-as-code tools that application developers routinely use to provision IT infrastructure. The challenge organizations are encountering is that much of that infrastructure is misconfigured in ways that enable cybercriminals to exploit vulnerabilities.

    Unfortunately, a recent Spacelift survey found that only 14% of respondents have fully implemented infrastructure automation best practices. The bulk of organizations, in fact, have simply created various islands of automation that they then attempt to manually integrate using multiple scripts, noted Hytry.

    Hopefully, with the rise of platform engineering, more of the management of infrastructure will become automated. A recent survey conducted by Futurum Research finds that adoption of platform engineering as a methodology for building and deploying applications at scale is gaining significant traction, with more than a quarter of respondents (26%) having mastered platform engineering, compared to 41% who are still working toward applying platform engineering across multiple projects. Another 24% are still working toward operationalizing a set of best practices for platform engineering, while 7% are just getting started.

    Roughly half of platform engineering teams provide cloud/multi-cloud management (52%) and dev/test/production environment support (48%). DevOps toolchains (43%), standard platform configurations (42%), and containers/Kubernetes (41%) support are also prevalent.

    Regardless of the approach to IT infrastructure automation, the need to unify the management of platforms has become a more pressing issue. Each platform an organization deploys tends to increase the total cost of IT simply because an additional team of IT professionals is usually required to manage it. Hopefully, as more artificial intelligence (AI) is applied to the management of IT infrastructure, the ability to scale those teams will significantly increase in the months and years ahead.

  • Secure Code Warrior Defines Security Rules for AI Coding

    Secure Code Warrior Defines Security Rules for AI Coding

    Secure Code Warrior has made available a set of security rules for application developers using artificial intelligence (AI) tools to generate code.

    Company CTO Matias Madou said the AI Security Rules made available on GitHub are intended to encourage developers to review code generated by AI for security issues that these tools may inadvertently introduce. Most AI tools were trained using samples of code that were randomly collected from across the web. As such, they can introduce vulnerabilities simply because they were trained using code that contains similar flaws, noted Madou.

    Additionally, the AI Security Rules encourage developers to establish guardrails that steer AI away from risky patterns and common security missteps, such as insecure authentication flows or failure to use parameterized queries.

    Previously, Secure Code Warrior has made available AI security training courses for application developers that Madou said will continue to be expanded.

    In general, AI coding tools have, from a cybersecurity perspective, plusses and minuses. AI coding tools are, for example, unlikely to introduce a SQL Injection vulnerability. In fact, there may come a day when this particular vulnerability is completely eliminated as AI coding tools become more widely used, noted Madou. However, AI coding tools also introduce other potential security concerns, including hallucinations.

    It’s not clear to what degree developers are relying on AI tools to generate code, but a recent Futurum Group survey finds that 41% of respondents expect generative AI tools and platforms will be used to generate, review and test code.

    Additionally, The Futurum Group finds organizations are exploring multiple paths to employing artificial intelligence (AI) capabilities across the software development lifecycle (SDLC). Over the next 12 to 18 months organizations plan to increase spending on not only AI code generation (83%) and agentic AI technologies (76%), but also existing familiar tools that have been augmented with AI.

    In effect, there is now a battle underway between incumbent providers of tools and startup rivals for the hearts and minds of software engineers.

    Regardless of how code is written, an application developer remains accountable for its quality. The challenge is that over time there is often a tendency to trust the output of an AI coding tool too much. Inevitably, the code generated might not only contain vulnerabilities but might also be deeply flawed in ways that might prevent an application from running at all. Just as challenging, AI coding tools might not be of much help when updating existing application environments simply because they might not have enough context to generate code that will work, noted Madou.

    On the other hand, there are many developers that only have a rudimentary appreciation for security issues. AI coding tools in those instances can significantly improve the quality of the code that might otherwise have been created by an application developer.

    There is, of course, no going back. AI coding tools are here to stay. The real issue is putting the guardrails in place that minimize any security vulnerabilities or other types of flaws that might compromise the security of an application.

  • Chronosphere Streamlines Management of Log Data to Reduce Costs

    Chronosphere Streamlines Management of Log Data to Reduce Costs

    Chronosphere today added additional capabilities to its log management platform that enable DevOps teams to both reduce costs and surface more actionable insights.

    Alok Bhide, head of product innovation for Chronosphere, said Chronosphere Logs 2.0 provides DevOps teams with more granular control over how log data is collected and stored. The overall goal is to make it simpler for DevOps teams to not only leverage analytics to identify which log data is actually being used but also more easily correlate it with metrics, events and traces, he added.

    Additionally, Chronosphere has added a Logs Quotas tool that enables DevOps teams to enforce budget restrictions on individual teams all the way down to specific datasets.

    Most DevOps teams are already being overwhelmed by the amount of telemetry data being collected, an issue that will only become more challenging to manage as more cloud-native and artificial intelligence (AI) applications are deployed in production environments.

    There is, of course, no shortage of observability platforms, but as IT environments become more complex, the need for tools that go well beyond simple monitoring of pre-defined metrics to troubleshoot applications has become a lot more pressing. The challenge is observability platforms collect data at levels of scale that from a cost perspective quickly add up. As a result, managing telemetry data has become a significant challenge. Unfortunately, most DevOps teams are not going to be able to hire someone to optimally manage the flow telemetry data. Instead, that needs to be a core capability of the observability platform.

    Less clear in the longer term is to what degree observability will become a task assigned to an artificial intelligence (AI) agent rather than a DevOps engineer. There is no doubt DevOps engineers will need to review the findings of an AI agent that has investigated an incident, but much of the tedious effort required to sort through metric, events, logs and traces should become increasingly automated. Each DevOps engineering team will then need to decide how comfortable they are allowing another set of AI agents to automatically remediate issues as they are uncovered, noted Bhide.

    In the meantime, organizations have never been more dependent on software than they are today, but even as the number of applications being deployed increases, the size of the DevOps teams tasked with maintaining them continues to remain relatively stagnant. In fact, in an AI era where more applications are expected to be deployed in the next few years than the entire last decade, supporting all those applications will require an ability to investigate and, if necessary, remediate anomalies within minutes of being discovered. Legacy monitoring tools were never intended to provide forensics insights in near real time.

    Of course, convincing business leaders to invest in observability platforms can be a challenge. DevOps teams need to be certain that the cost of storing massive amounts of telemetry does not outweigh the benefits. After all, no matter how many issues an observability prevents, someone in the finance team will still be closely monitoring the cost of a platform that over time only continues to grow.

  • Atlassian Adds CLI Option to AI Agent for Building Software

    Atlassian Adds CLI Option to AI Agent for Building Software

    Atlassian has added a command line interface (CLI) option to provide application developers with a familiar construct for invoking Rovo Dev, its artificial intelligence (AI) agent for building software

    Part of a portfolio of Rovo Software Agents that Atlassian now makes available in beta, Rovo Dev completes and debugs code, creates tests, surfaces insights and explanations of code bases, makes suggestions to improve code and generates documentation. It is also integrated with Jira project management software and Confluence collaboration tools provided by Atlassian.

    Using a set of software engineering (SWE) benchmarks maintained by researchers at Princeton and Stanford, Rovo Dev achieved a 41.98% resolve rate across 2,294 tasks.

    It can also be integrated via a Model Context Protocol (MCP) Server to access external data sources capable of providing more context that might be needed to complete a specific task.

    Shuyin Zhao, vice president of product for Atlassian, said the goal is to provide a single agent capable of performing a wide range of tasks versus requiring developers to create workflows that require them to orchestrate multiple agents to build and deploy software. The more memory that can be allocated to an AI agent the more it is able to preserve context, she added.

    Longer term, as the reasoning capabilities provided by large language models (LLMs) continue to expand, the scope of complex tasks that can be assigned to that AI agent will also increase, noted Zhao.

    Eventually, many developers will find they will be spending more time reading and evaluating code rather than writing it themselves, she added.

    It’s not clear how widely AI tools are being adopted by software developers and engineers, but a Futurum Group survey found 41% of respondents expect generative AI tools and platforms will be used to generate, review and test code. The one thing that is certain is more developers than ever are using these tools to write code, but how much of that code is making it into production environments is unknown. In some instances, an AI tool might enable a developer to write better code than they can on their own. In other instances, it might create vulnerabilities or recommend using software packages that simply don’t exist.

    Additionally, even as more code is generated, the existing DevOps pipelines might not be robust enough to deploy software at higher levels of scale than what is already being achieved.

    None of that means AI agents won’t be incorporated into DevOps workflows, but it does mean there is still a considerable amount of effort required to re-engineer those processes in a way that is optimized for AI agents rather than human application developers.

    In the meantime, however, DevOps teams would be well-advised to start creating a list of tasks they are willing to delegate to AI agents, assuming there is some level of supervision. Otherwise, it’s all but inevitable that AI agents might generate the same issues that human developers create, albeit just at a different level of scale. The issue then becomes making sure the right governance policies are in place to prevent as many of those issues from arising in the first place.