Please use this identifier to cite or link to this item:
http://10.1.7.192:80/jspui/handle/123456789/6856
Title: | Secure Access Testing & Automation |
Authors: | Chhatbar, Jaykumar |
Keywords: | EC 2014 Project Report Project Report 2014 EC Project Report EC (Communication) Communication Communication 2014 14MECC 14MECC03 |
Issue Date: | 1-Jun-2016 |
Publisher: | Institute of Technology |
Series/Report no.: | 14MECC03; |
Abstract: | USH (Unified Security Hub) is world’s first secure processor with integrated Radio Frequency IDentification (RFID) technology. It is designed to secure personal authentication transactions associated with physical access, logical access (into a PC or network) and contact-less payment applications. The USH also enhances the use of currently deployed authentication technologies, such as bio-metrics and contact-less technologies, by eliminating some of their inherent security vulnerabilities through encryption.The embedded USH performs all fingerprint processing on-board, eliminating the need for a bio-metric database while protecting the user’s personal privacy.The USH is compatible with 125 kHz proximity technology, 13.56 MHz contact-less smart card technology, Bluetooth(R) and USB. USH supports Ubuntu 12.04, Windows 7, 8, 8.1, 10 with processor architecture x64 and x86 so, it requires lot of testing procedures to follow up. USH testing consists application and device driver installation/un-installation and upgrade, Firmware upgrade, Power management, Stress test, WMI (Windows Management Instrumentation), Enrollment and authentication of Fingerprint, RFID and Contacted cards, Windows update, UEFI (Unified Extensible Firmware Interface), SDK (Software Development Kit) APIs, Windows Driver Certification. Manual testing is time consuming and it requires manpower at work, There are more number of chances of errors. If testing procedure is automated it will be true efficient and less error-prone. USH Automation use Server-Client topology, Test server launches python scripts remotely on DUT(Device Under Test) using RPYC (Remote Python Call). RPYC server will run on Client(DUT). |
URI: | http://hdl.handle.net/123456789/6856 |
Appears in Collections: | Dissertation, EC (Communication) |
Files in This Item:
File | Description | Size | Format | |
---|---|---|---|---|
14MECC03.pdf | 14MECC03 | 2.03 MB | Adobe PDF | ![]() View/Open |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.