ShieldProbe Fix
Fixes informed by
the actual attack.
Fix brings a supported application finding from ShieldProbe Assess into VS Code or Visual Studio (beta), with its attack evidence and a proposed patch. Your developers review it, test it and raise the pull request. Nothing merges on its own.
Switch between the code before and after the patch:
const order =- await orders.findById(- req.params.id- );+ await orders.findOne({+ id: req.params.id,+ ownerId: req.user.id+ });+ + if (!order) {+ return res.sendStatus(404);+ } return res.json(order);This is a proposal, not a deployed fix. Your developer checks it against your identity model, tenant boundaries and team-sharing rules.
VS Code, plus Visual Studio in beta. Example code with fictional data.
What Fix brings that a finding summary can't
- Attack evidence
- GET /api/orders/order-b07 → 200 OK, customer B's order returned to customer A.
- Source location
- The source file and line the finding traces to (routes/orders.ts), shown inline when source references exist.
- Proposed patch
- A diff you review, then a branch and pull request your developer raises.
A general assistant sees the summary. Fix also sees the attack.
Read the evidence
Fix / Review the patch
GET /api/orders/order-b07const order =
await orders.findOne({
id: req.params.id,
ownerId: req.user.id
});
if (!order) {
return res.sendStatus(404);
}The lookup now includes the signed-in owner. Review shared-team access policy before merging.
Developer review and branch tests required. Nothing auto-merges.
Representative Fix workflow
Your branch. Your review. Your release.
Your tests and approvals stay in place. A patch isn’t a fix until it has been tested.
Investigate the finding
Open the attack evidence beside the affected source. The sample report shows the kind of finding Fix starts from.
Review and test the proposal
Read the diff, run your tests and adapt the patch to your code.
Use your pull-request workflow
Push the branch and raise the PR in your configured provider. Your team reviews, merges and deploys.
Verify the correction
Replay the attack against your patched staging app. Check the owner can still read the order. Switch any Defend rule off first, so you test the code, not the shield.
Works in VS Code. Visual Studio in beta.
Fix proposes code changes for supported application findings. Your team fixes network and server findings using the report's remediation guidance.
For supported findings, Defend can protect while the fix is in review.
Questions about your IDE or repository setup? Book a Fix demo.
Questions developers ask
What does Fix need?
An approved finding with source-code context, VS Code 1.85+ or Visual Studio 2022+ (beta), and a ShieldProbe tenant with Assess or Continuous.
What access does it use?
You sign in through your browser with your ShieldProbe account. Fix reads the surrounding source in your editor. A pull request uses the git credentials already on your machine; the extension does not store your git credentials.
Where is code processed?
Inference uses Microsoft-hosted OpenAI models through Azure Foundry. Microsoft processes prompts and outputs; they are not made available to OpenAI.
Does Fix automatically create or merge a PR?
No. Your developer raises the pull request and controls merge and deployment.
How do we know the code fix works?
Run your tests, then replay the original attack and a normal user’s request against staging. In the Continuous developer preview that replay can run on the repository events you enable.
Bring the attack into the code review.
See how a finding becomes a patch your developers can review.