Skip to main content

Posts

N. Korea Group Behind Multiple Open Source Supply-Chain Attacks: Amazon

Amazon’s recent report attributing a series of compromises of open source software libraries to a North Korea-backed threat group encapsulates many of the expanding cyber risks increasingly facing developers, from the growing use of generative AI by bad actors and targeting of code repositories to financially focused attacks by nation-state hackers and the abuse of trust by development teams. It also is the latest report to point to the group – known by such names as Sapphire Sleet, Stardust Chollima, BlueNoroff, CageyChameleon, and Alluring Pisces – linked to the Democratic People’s Republic of Korea (DPRK) to supply chain attacks over the past couple of years that involve placing malicious code into packages in the npm repository. “When an attacker compromises a widely used open source package, every organization that depends on that package is potentially affected,” CJ Moses, CISO of Amazon Integrated Security, wrote in the report , adding that they have “observed the volume and s...
Recent posts

Common Risks of Outsourcing Software Development, and How to Tackle Them

Both SMBs and large enterprises often choose software development outsourcing over developing software in-house. It is no surprise, as partnering with external developers enables companies to bridge IT talent gaps that cannot be filled internally, avoid time-consuming recruiting and training processes, and eliminate expenses associated with salaries and benefits, eventually accelerating software delivery and reducing development costs. While software development outsourcing can be highly advantageous from the business perspective, it also introduces various risks, ranging from diminished project control to provider lock-in and security-related issues. Managing these risks proactively is critical to preventing them from escalating, minimizing their impact on the project timeline, budget, and software quality, and ensuring smoother project execution. In this article, experts from Itransition, an outsourcing partner with over 25 years of experience, outline common risks of outsourcing ...

Ten Great DevOps Job Opportunities

DevOps.com is now providing a weekly DevOps jobs report through which opportunities for DevOps professionals will be highlighted as part of an effort to better serve our audience. Our goal in these challenging economic times is to make it just that much easier for DevOps professionals to advance their careers. Of course, the pool of available DevOps talent is still relatively constrained, so when one DevOps professional takes on a new role, it tends to create opportunities for others. The ten job postings shared this week are selected based on the company looking to hire, the vertical industry segment and naturally, the pay scale being offered. We’re also committed to providing additional insights into the state of the DevOps job market. In the meantime, for your consideration. Dice Booz Allen Hamilton McLean, VA DevOps Engineer $77,600 to $176,000 Alarm.com Centennial, CO DevOps Engineer $120,000 to $130,000 HarbourVest Partners Boston, MA DevOps Engineer $135,00...

Microsoft Confirms Copilot ‘Super App’ Is Coming This Year — and It’s About More Than Convenience

Microsoft is finally admitting what many IT teams already knew: It has too many Copilots. CEO Satya Nadella confirmed on the company’s fiscal Q4 2026 earnings call, held July 29, that Microsoft is folding its scattered Copilot experiences into a single app. The move will merge chat, coding, the Cowork research tool, and Microsoft’s autonomous agents, called Autopilots, into one place, spanning both consumer and business use. “Copilot is evolving rapidly from chat to Cowork to Autopilots,” Nadella said. “This quarter, we are bringing these Copilot experiences together, including code, in one super app. This is a major step forward, and I look forward to sharing more soon.” That’s a real commitment, not a rumor. Nadella attached a timeframe, not a date. He named the four pieces going into the merged app but did not say whether it replaces Microsoft’s existing standalone Copilot apps or runs alongside them. Pricing, feature scope and rollou...

GitHub Brings Stacked Pull Requests Out of the Shadows

For years, stacked pull requests have been something of an open secret in software engineering. Teams at Meta and Google have used internal versions of the workflow for over a decade, and open source developers cobbled together their own approach with tools like ghstack. Now GitHub is making it a native feature. The company announced this week that stacked pull requests are in public preview, rolling out to all repositories over the coming days. The idea behind stacking is simple, even if the mechanics take some getting used to. Instead of building one large pull request that captures an entire feature, developers break the work into an ordered series of smaller PRs. Each one sits on top of the last, representing a single layer of the change. A schema update might be the base layer, with business logic stacked on top of that, and a UI change stacked on top of that. Reviewers can look at each layer on its own, without wading through a diff that spans a thousand lines. That distinction...

Open Source Code Just as Secure as Proprietary Software—If You Manage It Right, Says CISA

Open source can be just as safe as proprietary software, though government agencies (and private enterprises) should take additional measures to secure it properly, according to a new guide published by the U.S. Cybersecurity and Infrastructure Security Agency ( CISA ). The report, “ Open Source Software: Security Principles and Practices ,” provides with guidance to help agencies comply with two Presidential Executive Orders ( 14144 and 14306 ) which both urged them to do a more thorough job securing the software they use, a response to recent exploits like Log4Shell and XZ utils. CISA acknowledges that open source can provide immeasurable benefits to government agencies, not merely because it is available without licensing fees, but also because agencies can extend the software to meet their own requirements. But at the same time, open source software must be managed differently than proprietary software. Malicious hackers (and increasingly AI agents) use vulnerabilities to gain ...

Why Log Monitoring Is the Missing Link in Most Incident Response Workflows

Modern engineering teams have invested heavily in observability. Dashboards are populated, alerts are configured, on-call rotations are set. Yet when production incidents occur, the average time to resolution hasn’t dropped nearly as fast as the tooling has improved. The reason, in many cases, comes down to one overlooked gap: logs aren’t being used the way they should be during active incidents. This isn’t a tooling problem. Most organizations already have log data flowing somewhere. It’s a workflow problem, specifically, how logs integrate (or fail to integrate) into the broader incident response process. The Three-Tool Problem A typical incident response scenario looks something like this: an alert fires, the on-call engineer opens a metrics dashboard to understand the scope, then switches to a separate logging tool to investigate root cause, then jumps to a tracing tool to follow the request path. Three tools. Three contexts. Three sets of query syntax. B...