Hi,
As per the definition of logic obfuscation, obfuscated circuit stays in obfuscated mode upon global reset (i.e. initial state) and generates incorrect output; upon receiving correct initialization sequence it enters into functional mode and generates intended outputs.
This is fine with respect to the design that does not connected with any further critical systems. If at all, the obfuscated logic needs to be connected to further safety critical systems, won't incorrect value generated in obfuscated mode affects the critical systems??
In such case, how to apply logic obfuscation??
Thanks in advance.
Dear Sumathi Gokulanathan,
I suggest you to see links and attached files in topic.
-SECURITY THROUGH OBSCURITY - Semantic Scholar
https://pdfs.semanticscholar.org/.../7960e74e5f1436b31f2b804313...
-Enterprise Obfuscation Technology, Process and Control - PreEmptive ...
https://www.preemptive.com/.../Enterprise-Obfuscation-Technolog...
-Hardware Obfuscation
https://www.emsec.rub.de/media/.../04/.../HardwareObfuscation.pd...
-A Systems Approach to Cyber Security: Proceedings of the 2nd ...
https://books.google.dz/books?isbn=1614997446
Best regards
An attacker is an abstract interpretation of the program on an abstract domain of approximate data. It is known that the precision of an abstract interpretation is determined by the chosen abstract domain. For this reason we identify attackers with abstract domains. In this scenario, obfuscating a program with respect to an attacker specified as an approximate (abstract) interpreter means making this interpreter imprecise. This is precisely modelled by the notion of incompleteness of an abstract interpretation.
For more details read click
https://link.springer.com/content/pdf/10.1007%2Fs00165-016-0374-2.pdf
Previous answers are very off topic, the question relates to hardware security and logic locking as means to achieve obfuscation.
First thing one has to assume is that there is an SoC in place, as every modern chip is an SoC. The SoC itself is the center/brain of the critical system. Second, logic locking is applied selectively, not to the whole chip. One module out of N modules will be obfuscated, typically. The effect of that module on the system is well known and can be easily managed. This is trivial. For instance, as long as you make sure your locking doesn't propagate control signals down the stream, instead only corrupts data, you will be safe.
Please understand that this is a student asking a question, and being so, staying on topic is far more helpful to her and others that may read this at a later time.
I politely pointed out that your response (and the ones of others) are not on topic. In your first post you even made very clear that you don't know what logic obfuscation is... Self-criticism goes a long way, you know.
Had you looked at at the OPs previous posts (which are in hardware security) you would know what she is asking. Even her tags point in the right direction.
She is talking about the addition of key-controlled XOR/MUX gates to an existing circuit such that it only operates correctly if the right key is provided. The actual circuit is irrelevant, it can be anything.This is a CLASSICAL technique in hardware security, referred as logic locking or logic obfuscation. The (main) adversary for which this technique was devised is the untrusted foundry that will fabricate your chips. If they overproduce your chip, the additional units cannot be activated. If they try to sell your IP to someone else, it also cannot be activated.
You can read the literature yourself and come up with your own conclusions. It would do you good, you would sound less like a non-expert rambling about something you have very little clue about. I am done here.
- Badges
- Science topic
- Similar topics
- Computer Science and Engineering
- Algorithms