>>
|
701a19.jpg
Spice Candy
701a19
>>160125
Er... You don't actually understand how these things work, do you. Having hardware that supports a full link doesn't present any risk unless the system was designed by a Hollywood director.
There's two controls, and they work in tandem:
The first is outgoing control, which is where the device decides what should and should not be sent. Basically, it boils down to "Don't send anything you don't want to send.
The second is incoming control, which is where the device analyzes incoming data to determine if it meets the metrics to be accepted. In systems not designed by people who are utterly incompetent, that means that the system will reject everything that isn't explicitly listed as accepted. Part of those metrics include authentication; that's one of the reasons why asymmetric encryption is so good for these kinds of things.
These metrics can extend into content-aware checks, meaning that data that doesn't conform to normal operation can be filtered.
Past basic transmission controls you have further validation, which includes sanity checks, input sanitation, range cropping or attenuating, and other such actions.
Beyond that you have response-based controls, which includes monitoring the internal system state for abnormal status and closing connections in the event of a fault.
The difficulty of creating a secure system is proportional to complexity of the system, and inversely proportional to the priority of making the system secure.
Almost all computer security problems stem from user error, and we are going to be the ones managing this system. Ashley has the other end, but give her a few days to research this at a public terminal and she'll be fine.
|