Cleared
Yes for the tested use. We found no issues that block it.
Platform / Device clearance
Know every device before it joins your network.
Test the device for the way you plan to use it.
Before you connect a camera, drone, or sensor, NetOps IQ tests it for the way you plan to use it. You get one of four clear answers, the evidence behind it, and what to do next.
The decision record
Yes. Yes, if. No. Not enough evidence yet.
Conditionally cleared
Yes, after you meet the conditions in the report. These might include updating the firmware or restricting access.
You get a specific action list and a way to check completion.Not cleared
No. Don’t use the device as planned.
We explain what failed, what needs to change, and what to retest.Insufficient evidence
Not sure yet. We could not test enough to decide.
We tell you what is missing and how to reach a decision.How it works
How we test a device and report the result.
- 01
Submit
Identify the device, firmware, intended use, and decision needed.
- 02
Authorize scope
Agree what we will test, what access is needed, and what the device must do.
- 03
Test
Perform agreed checks and record findings, evidence, and incomplete tests.
- 04
Decide
Give a clear outcome, explain why, and identify who approves deployment.
- 05
Report
Deliver the findings, evidence, conditions, and next steps together.
- 06
Retest date
Set the next review date and change events that trigger earlier testing.
The deliverable
What your report includes.
Device identity
Model, firmware, configuration, ownership, and intended environment.
Authorized scope
Permitted tests, methods, acceptance criteria, exclusions, and test dates.
Findings and evidence
What was checked, what was observed, evidence references, and incomplete work.
Decision and rationale
One of four outcomes, known blocking findings, and the named decision owner.
Conditions and follow-up
Restrictions, required actions, accountable owners, and due dates.
Retest plan
An agreed review date and events that require reassessment sooner.
FOR PROCUREMENT & RISK TEAMS
Test before you buy.
Then check three things before you sign.
Testing after a device is installed is costly and disruptive. Test it first, and the findings become leverage while you still have purchasing choices.
Match the test to the purchase.
Check that the model, software version and intended use in the report match what you are buying. A different configuration may need another review.
Know who will support it.
Review how the vendor ships updates, handles reported problems and supports the device over its life. Include data handling in that conversation.
Write the conditions into the contract.
If a device is conditionally cleared, put those conditions in the purchase terms, with an owner for each and a way to check it.
One record shows security, procurement and oversight teams the same evidence, so nobody rebuilds the decision from emails and spreadsheets.
DEVICE ASSESSMENT
Know what you’re approving.
We reviewed a drone’s software and tested the device in an authorized lab. The tests showed that stored device data could be accessed. They also showed which suspected problems could not be confirmed.
The report explained what we found, what still needed testing, and what should change before a decision about using the drone.
Review the assessment summaryQUESTIONS
What happens after the decision?
What does “Cleared” mean?
Our tests found no issues that block the use described in the report. You get the findings and evidence so your team can review the decision.
What is the difference between “yes, if” and “not sure yet”?
Conditional clearance gives you a decision with specific requirements to meet. Insufficient evidence means a test or access is missing, so we cannot reach a decision yet. In either case, we explain the next step.
When should we retest?
A software update, new configuration, different use, or newly identified threat can change the answer. Your report lists the changes that call for retesting and the next review date.
How does this fit our approval process?
Device Clearance works alongside your normal certification, regulatory, procurement, and insurance reviews. Your authorized owner makes the deployment decision using the findings and any conditions in the report.
What do you need before testing?
Tell us the model, software version, and intended use. We check which tests we can perform and agree on access with the device owner. You approve the testing plan before work starts; any changes need separate approval.
Start with one device and one intended use.
Tell us what you plan to connect. Get a clear decision and the evidence to review it.