Introduction to child-proofing (i.e., protecting the appliance from the end-user)
How to perform child-proofing of an appliance prototype is definitely one of my favorite conversations to have with product teams. Please indulge me and allow me to elaborate. This process may be the single greatest factor in determining what meets the definition of an appliance. All efforts to keep the final solution secure and focused solely on its predetermined function are crucial. The end-users must be properly guided on the initial setup requirements and kept within your guardrails of what you choose to allow them to access beyond the application/function of the appliance.
There are many efforts to be considered here. How will my product’s end-users actually access the solution? What can be done to minimize or prevent any end-user from obtaining unauthorized elevated or root access? What automation will need to be put in place and obscured via the appliance’s UI?
A prime example...
