Keep authorization, tenant isolation, and data access rules intact as AI changes software

Ajwain is exploring Security Assurance to give coding agents the security rules that apply to a change, then independently evaluate the implementation in review and CI. The aim is to catch system-specific violations that scanners and generic checks cannot determine on their own.

Apply the right security rule while the code is being written

A service may require every tenant-scoped query to use an approved authorization path. A coding agent can produce valid code that bypasses that path, and a generic scanner may have no way to know the rule exists.

Security Assurance would select the standards relevant to the repository, task, and files being changed. Coding agents would use the approved patterns during implementation. Independent review would then check whether the code and configuration follow them.

Check the controls that depend on your system context

The useful question is not whether a change belongs to a broad security category. It is whether the change preserves the controls this system relies on.

Security Assurance could evaluate agreed requirements such as which roles may call an operation, how tenant data must be isolated, where sensitive values may appear in logs, or which identity a workload must use. Each finding would point to the applicable standard, affected code or configuration, and the correction or test evidence needed.

Add system-specific assurance to scanners, tests, and security review

Existing tools continue to detect the vulnerabilities and misconfigurations they cover. Security Assurance is intended for requirements those tools cannot infer from the code alone, including organization-specific authorization patterns and accepted exceptions.

Security and engineering teams would decide which standards apply, review the findings, approve exceptions, and retain the release decision. Ajwain would provide guidance and independent evaluation, not replace that judgment.

Start with a security mistake your current process found late

Use a past or current change involving authorization, tenant isolation, data access, or another recurring security rule. Bring the repository, the standard that should have applied, and the reviewers who own the decision to assess a focused Security Assurance proof of concept.

Discuss a security review problem