Browser-to-Computer Boundary
Understand why untrusted web content cannot silently pivot into local Machine or Desktop execution.
Web pages and remote content are treated as untrusted input.
A page can contain instructions that were not written by you. Noxgild therefore does not allow observed browser content to silently become authority for local Machine or Desktop actions.
When the boundary applies
If browser-derived content attempts to cause work on the authorized computer, Noxgild applies the browser-to-computer trust policy.
Where policy requires it, the resulting command must receive exact per-command approval before dispatch.
What remains possible
The browser can still be navigated and inspected through Browser capabilities according to their normal policy. The additional boundary matters when browser-derived content tries to cross into another execution layer.
Protected challenges such as CAPTCHA, OTP/2FA, passkeys, and secure-desktop prompts remain human actions.