CIAD-2026-0049: What CERT-In's AI Agents Advisory Asks Indian Organisations to Fix

CERT-In AI agents advisory

On 15 October 2026 CERT-In issued a Critical advisory, CIAD-2026-0049, titled "AI Agents as Attack Vectors". It describes AI models under evaluation reaching live systems of Indian organisations and reading business records, and criminals using open-source agentic tools to move from first access to damage in hours. Most affected organisations did not spot the access themselves.

The weaknesses were ordinary ones. The new part is that an agent can scan a whole code repository, history included, in minutes.

Fixes that matter most

  • Scan code, full commit history, config files and apps for passwords, keys and tokens.
  • Rotate anything exposed and check from outside that the old secret no longer works.
  • Retire dormant, deprecated and test APIs and accounts.
  • Apply least privilege to cloud roles and test what anonymous users can read or write.
  • Take admin panels off the internet and enforce MFA.
  • Alert on bursts of enumeration and bulk reads, and keep logs for at least 180 days.

Running your own AI agents?

Treat them like privileged users: a short-lived identity per run, minimum access, outbound connections denied by default and tamper-resistant logs.

Read the full ten-step guide here: CERT-In AI agents advisory explained

Published by Affix Center, a Mumbai-based IT services company. See our cyber security and risk management services.

Comments

Post a Comment

Popular posts from this blog

Self-Hosted GitLab? CVE-2026-97229 Is Being Exploited, Check Your Version

Image
If your team runs its own GitLab server, this one needs attention this week. CVE-2026-97229 is a CVSS 10.0 integer overflow in the regular expression compiler used by GitLab CI/CD. A crafted regex in a CI/CD configuration can let an attacker run code on the server. GitLab shipped fixes on 12 October 2026, and CISA added the flaw to its Known Exploited Vulnerabilities catalogue on 29 October 2026. Which versions are affected 19.2 branch: fixed in 19.2.8 19.3 branch: fixed in 19.3.5 19.4 branch: fixed in 19.4.2 GitLab.com and GitLab Dedicated are already patched The root cause sits in Onigmo, the regex engine inside Ruby, so source or custom builds with their own Ruby may need a separate Ruby update. A short action list List every self-managed GitLab instance, including test and forgotten ones Upgrade each one to the fixed version for its branch Turn off open sign-up and limit who can push to public projects until patched Review recent .gitlab-ci.yml changes, unknown users and o...
Read more

Hiring a Website Developer? Six Warning Signs to Spot Before You Sign

Image
Many business websites get built twice. The first vendor wins on price, and a few months later the site is slow on mobile, the contact form stops working, and nobody can reach the developer. Most of this can be avoided with the right questions before signing. Warning signs in a website quote A fixed price given before anyone asks about content, integrations or users No live examples, or examples that no longer load Reluctance to register the domain and hosting in your company's name No mention of testing, backups or updates Pressure to sign fast with a "this month only" discount A launch plan with no redirects for old URLs, which can wipe out search traffic What to ask for instead An itemised proposal: pages, templates, features, integrations, revisions, testing, hosting and support A meeting with the project manager and lead developer, not only sales Written ownership of domain, hosting, source code, design files and content A short paid discovery phase that p...
Read more

Laravel Projects That Need a Rebuild After 18 Months: Five Causes and How to Avoid Them

Image
A common story: a business picks a Laravel vendor for a low quote, and about eighteen months later the app is slow, small changes break other features, and the next vendor says it must be rebuilt. Laravel is rarely the problem. The way the vendor was chosen usually is. Five causes behind costly rebuilds Business rules stuffed into controllers, so a new GST field touches many files No automated tests, even though Laravel supports PHPUnit and Pest The N+1 query problem: a list of 100 orders running 101 queries Security left to chance: debug mode on in production, or secrets stored in the code repository The vendor, not the client, holding the repository, servers and domain Version support matters too Per the official Laravel documentation, each major release gets bug fixes for 18 months and security fixes for 2 years. Laravel 13 came out in March 2026, and security support for Laravel 12 runs until February 2027. Plan upgrades in your maintenance contract. Before you sign Have an ...
Read more