Set your browser minimums.
Set the oldest browser versions you support, then check which security features they can use. Known limitations and missing data stay in the results. Your plan stays on this device.
Choose your browsers
Include each browser you support and choose its oldest accepted version. These are your policy choices; ControlCurrent does not detect the browser you are using.
First visit? Try a worked example.
Chrome 120, Firefox 115, and Safari 17
Select Load example, then Check support. Results are grouped into features that are ready, need care, are not supported, or do not have enough browser data.
- Choose: load the three example browser minimums.
- Read: open “Why?” to see the browser-specific evidence.
- Act: follow the next step and keep the stated fallback.
Keep a few plans
Up to 12 named plans. Saving is optional. Header input and evidence are never included.
What your browser choices can support
Turn this result into a reviewable browser policy
Choose what your project requires
Select required security features, decide how uncertain browser data should be handled, and record any temporary exceptions. The policy and report are generated on this device.
Policy decision
Review the canonical policy JSON
Check the exported policy in continuous integration
Attach a privacy-reduced evidence result
Add either a reduced evidence report or a command-line evidence-policy result. ControlCurrent keeps browser availability and supplied configuration evidence as separate sections. It does not calculate a combined security score.