Privacy issues in RFID technology
The RFID privacy issue is not only whether a number will be read by itself, but also whether it can be permanently associated with an individual, itinerary or consumer behaviour.
Privacy risks are derived from the relevant data chain
The low number of data on the label does not mean that there is a small risk; stabilization marks can also create sensitive inferences if connected to back-office personal data.
A reduction in reading distance would reduce some of the by-reading opportunities, but it would not be a substitute for minimizing collection, delegation of authority and audit, nor would it eliminate the risk of back-office account abuse.
Privacy risks often come from intersystem connections, not just label memory. A number that links continuously to shopping, access and identity information can increase exposure. It should limit use, access and save the range, and keep the path to correct errors and unconnection.
Identify the number. It's a few steps away from proving it's true.
Reading a valid number only indicates that the system receives a format-compliant identity information; to improve authenticity, authentication of documents, labels and physical bindings, and flow records should continue. The case is strong, reading distance is shorter or labels are difficult to remove, and cannot be a separate alternative to access control and key management.
Change the security promise to a testable attack.
“Security” should describe what is being protected, who is facing it, and what fails. For example, the only way to prevent unwittingly wrongfully taking is different from the design required for those who prevent conditional dismantling and reproduction. Certification can only prove that a document meets the rule, but also requires confirmation that it is not improperly separated from the physical; back-office logs can only prove that the operation was recorded and limit who could modify the log. The more clear the path of attack, the easier it is to find weaknesses, the easier it is to justify the risks that cannot be covered, and to avoid holding one security measure accountable.
Re-examine the programme from an exception
An anonymous number can connect the same object over time, and if connected to a purchase record, it may involve personal behaviour. Therefore, privacy assessment cannot only check for names. Ask who is necessary for the task, who has the right to establish it, and when should it be removed.
Put your judgment in the real situation.
Lists the sources and users of each data type, attempts to extrapolate personal information from read-only numbers and check whether unnecessary connections can be removed.
It is recommended that the design be reversed from the act(s) to which it was intended: copying number(s), transplant label(s), counterfeit and internal modification of the record(s) are tested separately.
From demonstration to delivery, what evidence is needed
| Observation dimensions | Evidence to be retained |
|---|---|
| Threated object | Make it clear whether the opponent can read and write, dismantle or contact backstage |
| Credible evidence | Cross-validation of certification results and business records |
| Dismissal disposal | Losses, cancellations, bid changes and audit enforceability |
| This is the key trade-off. | Does the system have to know who this item belongs or does it need to be known in a given mandate that it can be used? |
It's worth asking.
Does the system have to know who this item belongs or does it need to be known in a given mandate that it can be used?

Ms. Lei
Mr. Pang