Abstract:
This invention proposes novel systems, methods and apparatus that utilize smart devices (e.g., smartphones) capable of reading/processing biometric inputs, and wireless communications over secure, short-range wireless channels (e.g., near field communications (NFC)) to securely access websites and cyber-physical system (CPS) entities such as vehicles, rooms and control knobs as well as sensors and smart meters. A user accesses a website on a display terminal or CPS entity by using her smart device to send her biometric credentials to request access for a service, and communicates with either the said terminal or the said CPS entity which is also capable of short-range wireless communications, using secure and short-range wireless channels to ensure the authenticity of the user when using the service. This system also protects the stored credentials of the user against loss or theft of the smart device since the credentials are encrypted by the user&#39;s biometrics, and the stored credentials on the smart device can only be accessed by a legitimate user using her biometrics.

Description:
RELATED APPLICATIONS 
       [0001]    This application claims priority to Provisional Patent Applicant, Ser. No. 61/642,530, filed May 4, 2012. 
     
    
     FIELD OF INVENTION 
       [0002]    The invention pertains to securely access to websites or other cyber-physical assets. The invention is also directed towards using smart devices (e.g., smartphones) capable of reading/processing biometric inputs, and wireless communications over secure, short-range wireless channels (e.g., near field communications (NFC)) to securely gain access to websites and cyber-physical system (CPS) entities and control them. CPS entities in general are assets whose access is controlled by a lock mechanism such as vehicles, rooms and control knobs as well as sensors and smart meters. This invention also relates to improvising the means for reducing the risk of misuse of assets, and for protecting related apparatus, including measures to minimize leakage of credentials, identity theft and other forms of fraud. 
       BACKGROUND OF THE INVENTION 
       [0003]    Most Internet services like email, e-banking and social networking implement access control via a username\password based authentication scheme. Recently, new classes of passwords such as Graphical, Haptic and Visual have been proposed to replace textual passwords which are plagued by human fallibility. While promising and efficient in standalone applications, these new class of passwords are not likely to be used in the foreseeable future, due to the requirement of new hardware, usage education and interoperability with current systems. Textual passwords thus are likely to remain at least for now as the only way to authenticate a user to web services. However, an adversary, by gaining knowledge of a user&#39;s password (e.g., by brute force attack), can compromise a user&#39;s access to such services. This concern can be largely alleviated by having users choose strong and complex passwords (which have high information entropy) for authentication. In fact, some Service Providers have enforced password creation policies to make users choose such strong and complex passwords. 
         [0004]    However, there are two inherent issues with users being forced to choose stronger (or complex) passwords. First, studies such as [1]-[4] have indicated that enforcing stricter password rules causes users (almost 50% according to [5]) to take shortcuts like writing down the complex password in clear text, either on paper or electronically, as a memory aid. 
         [0005]    Thus, it is easy for an adversary to get hold of the complex password[1],[6]-[8]. 
         [0006]    The second issue with complex passwords is the reuse or recycle of the same password for different services since remembering different passwords is burdensome. More than 34% of the people reused the exact password while almost 18% reused them with minor modifications [5]. The study in [9] also found that 41% of accounts from a university system could each be cracked in three seconds, using the knowledge of their expired passwords. A malicious entity can thus easily crack a user&#39;s password if she has the knowledge of password composition trends by the user or (and) if passwords are reused. 
         [0007]    To add to this, the risk of compromising her password either from shoulder surfing techniques [10] or key loggers on end systems always exists, especially in public places or systems [11]-[12]. In shoulder surfing, an adversary is able to watch a user keying in her credential by visually recording the user&#39;s keystrokes. Keyloggers are programs or hardware devices that record all keyboard strokes. 
         [0008]    However, the most serious problem today is that current authentication systems have no mechanisms to recognize the identity of the person who enters the password; in other words, there is no way of verifying if the person presenting the credentials is actually the person that she is claiming to be. Since the communication channels can be secured using protocols such as https, SSL, TLS, the weakest link which controls a user&#39;s access to web services today is the human factor [13] due to the need of entering passwords. 
         [0009]    Similarly, access to Cyber physical system to authorized personnel is controlled using smart card readers or physical keys to provide access to the CPS entity. However, any unauthorized person can gain access to the CPS entity by gaining possession of the smart card or the physical key that provides the access to the CPS entity. 
         [0010]    Currently, in order to incorporate a new authentication schemes, such as using a person&#39;s biometric attributes like fingerprint, iris scan etc., to existing authentication schemes to access websites or CPS entity would require a change in the present internet architecture or installation of readers that is capable of reading a person&#39;s biometric attributes like the fingerprint. It is not feasible to achieve this. 
         [0011]    This invention addresses these problems by incentivizing the usage of strong passwords effortlessly, tying up a user&#39;s digital identity to her physical identity and assimilating emerging technologies such as smartdevices (capable of reading and processing the user&#39;s biometric inputs) the and cloud services into current existing technologies to realize a secure system, capable of securely accessing websites or other cyber-physical assets. 
       DESCRIPTION OF RELATED ART 
       [0012]    Securing access to an asset is a well-known problem and a lot of solutions have already been proposed. Particularly, U.S. Pat. No. 8,0037,511, US 2009/0158032, US 2006/0224901, and U.S. Pat. No. 7,5552,467 have proposed approaches/ solutions for securely accessing assets using mobile phones or similar devices. In the following paragraphs, we describe how our approach differs from them. 
         [0013]    In the case of U.S. Pat. No. 8,0037,511, the invention uses a mobile phone as additional authentication mechanism to web services and assets. In the scenario of accessing web service, a user has to register her phone to a service, apart from username/password credentials for authentication. This is so that secondary authentication details can be provided/processed via the mobile phone, this thus forces a user to always have the mobile phone to access the webservice. Second, any unauthorized user who gains possession of the registered phone can use it to authenticate her to the web service. In our invention first no such registration is necessary, providing the user with the convenience of not always having the smartdevice on her person and allowing access to services in case the smart device is not operational for any reason. Second, our invention also mandates that a user has to authenticate herself to her smart device via biometrics. This prevents unauthorized access to services in cases where the user loses or misplaces her device. Further, our invention also requires that the credentials of a user are stored on a smartdevice, which further minimizes the threat of identity or credential theft. Another important distinction of our invention from U.S. Pat. No. 8,0037,511 is that there is no need for changes to existing service providers (such as service providers requiring to process additional authentication mechanisms) or architectures. Our invention can be used on top of existing architectures perfectly. Further, the use of additional authentication factors also increases the chance of compromise as there are more avenues to exploit. Finally, our invention also addresses the security scenarios after a user has successfully authenticated to web services. In our invention after successful authentication a user is leashed to the host terminal via Bluetooth. If a user walks away from the host terminal with her smart device, the user is automatically logged out of the service and re-accessing the service requires the user to authenticate again. 
         [0014]    In the scenario of Cyber Physical Systems or assets, our invention allows flexibility of user-specific authentication (say, more than one biometric attribute) as opposed to the keyless entry concept provided by U.S. Pat. No. 8,0037,511. Further, our invention allows access to systems via a reservation system which in case of personal assets such as cars, apartment access, etc. eliminates the need of an owner to be involved during the authentication process. However, in such cases the owner needs to be involved in the reservation process. As before, our invention uses biometrics exclusively for accessing physical assets thus minimizing unauthorized access. 
         [0015]    US 2009/0158032 also presents a method for securing access to online services to users of mobile communication terminals, however their solution is aimed more towards the workings of securing access to mobile data networks and wireless mobile data networks. Our invention assumes that the access to data networks is already secured. 
         [0016]    US 2006/0224901 provide a solution aimed at using mobile devices in an access control system. Specifically, the invention aims at controlling access to assets, places or things by having credentials remotely assigned and revoked. The difference between their invention and our invention is two-fold; first, they do not use biometrics for authentication, which increases the risk of unauthorized access to assets. Second, access control rules are sent to the mobile device instead of the CPS entity, which is a dumb tag and only transmits its identity. The controller updates the access information on the user&#39;s device, which reads the identity of the CPS entity/asset and determines if it (and thus, the user) has access to the entity based on the access control rules. In our invention, the CPS entity processes the credentials presented to it and it determines if the user has access to it, which again minimizes risk of unauthorized access. 
         [0017]    U.S. Pat. No. 7,5552,467 present a solution that is aimed more at user interfaces for configuring access criteria and security rules responsive to primary and secondary passwords. Thus the said invention aims more at 
       SUMMARY OF THE INVENTION 
       [0018]    The following paragraphs describe the methods used for authenticating users for access control to assets and services, which include web based services as well as cyber-physical entities. 
         [0019]    The primary approach is to allow users gain access to services by authenticating to service providers using their smart devices. Smart devices in addition to possessing the processing capability and memory that rival modern computers also have optimized modules to efficiently use their limited energy, thus providing longer standby time. Many smartphones like the Motorola Atrix, come equipped with biometric sensors like fingerprint readers as well as features such as face-unlock, to authenticate the use of the smartphone. With the use of smart devices, the need for setting up dedicated Biometric authentication is not required, hence circumventing its major drawback of costly installations. 
         [0020]    In case of accessing web based services, a user will want to access the web services on a Host Terminal (HT). Here the Host Terminal is used to view the web content. The user uses her smart device to connect and communicate to the HT using a short range wireless communication such as NFC, BlueTooth etc., and uses the short wireless communication protocol to securely transfer her credentials to the HT which then forwards it to the required web service. The flow of information from the Host Terminal to the web server is securely processed via Internet protocols. Similarly, the authentication mechanisms and schemes at the web server are unchanged. Thus the inventions approach also mainly addresses the interaction between a user and the Host Terminal for accessing services. Specifically, we address the problem of inputting credentials via a Host Terminal to access a service. Incidentally, addressing this specific problem also addresses the limitation of memorizing textual passwords. SESAME provides an avenue that is complimentary to textual passwords and their usage, mainly providing a way to better support its use while removing their limitations. A user during the registering process for a web service chooses a strong password. She then stores her credentials for the service (username and strong password) on a smart device by manually entering this information. Whenever she has to access the web service, she will securely transfer the credentials from her smart device to a Host Terminal or a cloud service which will then forward her credentials to the appropriate Service Providers. The Service Provider authenticates the user and delivers the service to the Host Terminal. This concept can also be extended to the use of biometrics as credentials for authentications. In this approach, the user uses the smart device to input, process her biometric information and registers the processed biometric attribute as the authentication credential with a web service. Whenever the user wants to access the web service the user now presents her biometric information via the smart device as authentication credentials. The webservice processes the biometric information and accordingly grants or denies access to the user. 
         [0021]    In case of the Cyber Physical Systems (CPS), the overall approach still holds true. Any user wanting to access a service will use her biometric exclusively as her authentication credential. The user when accessing her service will have to save her biometric attribute on a smart device as credentials. The user will then user her smart device to communicate with the CPS entities and using short range wireless communication such as NFC, transfers her credentials for authentication. The CPS Entities then can process the credentials and accordingly grant or deny access to the user. This particular approach can also be used by a user to reserve access to a CPS entity, where initially the user can send across her biometric attribute as a registration token/credential to the service provider or owner of the service. At the time of using the service, the user follows the same method to authenticate herself to the service provider. 
     
    
     
       DESCRIPTION OF THE DRAWINGS 
         [0022]    Drawing  1  depicts the operation of SESAME, with numbered lines describing the order in which a user has to use SESAME to gain access to a website or a CPS object. 
           [0023]    Drawing  2  describes the apparatus and method for user wanting to access a web service and how the web service provider (or any service provider) can authenticate her. 
           [0024]    Drawing  3  describes the apparatus and method for a user wanting to access a web service in the presence of a cloud service, how the web services (or any service provider) can authenticate the user and how the web service can be delivered to the user. In presence of the cloud service, the web service can deliver the required service to the user either via the cloud service or directly from web service to the user. 
           [0025]    Drawing  4  depicts the system and method for a user to register her biometrics (used as credentials) with a Web service (or any service provider). 
           [0026]    Drawing  5  depicts the system and method how a web service (or any service provider) authenticates a user when a user has already registered her biometrics with a web service (or any service provider) and wants to access a service. 
           [0027]    Drawing  6  depicts the system and method to securely reserve and access a physical entity in the presence of a reservation service. It also depicts the authentication of a user in such a scenario. 
           [0028]    Drawing  7  depicts the system and method to securely sharing a CPS resource or asset in the absence of a reservation system. This system primarily caters to sharing of personal physical resource or assets of an owner. 
           [0029]    Drawing  8  depicts the system and method to securely access a CPS resource or asset in the presence of an owner and a reservation system. The drawing also depicts authentication methods. 
       
    
    
     DETAILED DESCRIPTION OF INVENTION 
       [0030]    Reference will not be made to several embodiments of the invention with examples of scenarios, described here and illustrated in the drawings. 
         [0031]    The following are the definitions of some basic objects along with their notations in parentheses, that will be recurring from here on. 
         [0032]    User (U) and User&#39;s smart device (D) e.g., smartphone, which is capable of reading/processing biometrics. An owner (O) of a CPS entity is also considered as a user when she wants to use the entity (instead of letting others to use the entity). 
         [0033]    User Agent: this could be another human e.g., the owner (O) of a CPS entity, or a software agent as a part of the cloud service (CS). 
         [0034]    Service (S) e.g., websites for E-mail, E-Commerce, Social Networks, or Resource (R) e.g., CPS entities. 
         [0035]    Service agent: this could be a Service Provider (SP) e.g. web servers or a resource management/reservation system (RS) used for CPS entities. 
         [0036]    Near Field Communications (NFC) interface or any other short range wireless communication mechanism such as Bluetooth. 
         [0037]    Biometric Hash (BH) generated by the user&#39;s smart device (D) with user&#39;s biometrics U BIOMETRIC  and a “salt” used to add certain randomness to the BH. 
         [0038]    Other definitions will be made as and when the embodiments require their usage. We first describe the embodiments of a Website access system and then the embodiments of CPS access systems. 
       I. Website Access Systems 
       [0039]    Drawing  2 , depicts a access system for a web service operated by a service provider (SP). The access system comprises of user U, her smartdevice D (which adheres to the definitions/requirements mentioned above) and an electronic device (or other embodiment of a client) with capability of connecting to the service provider over the Internet or other data communication networks, such as a computer with short range wireless communication interface, here marked as the host terminal (HT). The host terminal is used to process the service provided by the service provider, only if the user is authenticated to the access the service. The service provider may be using security services or servers to confirm authentication credentials. We assume that U already has stored her strong password/credentials (CR STORED ) on D along with the service attributes for each service. D stores the credentials (or any other embodiment of credentials) what herein will be referred to as a password file and encrypts it using a BH created from a user biometric (U BIOMETRIC ). We also assume that U has stored on D, her BH (from U BIOMETRIC ) that is used to authenticate U to D. 
         [0040]    U first presents her biometric attribute (such as a fingerprint scan/face unlock or any other embodiment of the same) to D which reads the Biometric input, calculates the Biometric hash (BH) and compares it with U BIOMETRIC . On successful comparison, D is unlocked. If U uses other means of locking the smart device such as a pin code, graphical passwords etc., U has to present them for D to be unlocked. The user then provides to D the attributes of a service such as the service name or identifying information (or any other embodiment of such attributes) as well the biometric required decrypting the password file that contains the credentials necessary to access the service. D reads the biometric, generates a BH and uses it to decrypt the password file. If the attempt is successful the password file is decrypted and U is notified of it. U then initiates a short range wireless communication connection to the host terminal using D. On successfully creating a connection, U is notified of this. U then requests for opening the service, by transferring to HT the service attributes and credentials stored on D (CR STORED ), via the short range wireless communication. The host terminal, then forwards the credentials to the service provider using the Internet or similar data network. On receiving the credentials from the host terminal, the service provider, uses them to authenticate the user by comparing CR STORED  and CR SERVICE  (stored when U registered for the service with SP) and accordingly grants or denies access the service. The notification of the result of the authentication is provided to the host terminal only. If successful, the service provider provides the service to the Host terminal. 
         [0041]    D after transferring the service attributes to the HT, locks itself to prevent unauthorized access, however it still maintains the short range wireless communication connection it has maintained with the host terminal. The host terminal also maintains this connection with the D. This process is referred to the leash from here on and will be used by both the HT and the D to monitor U&#39;s proximity to HT. 
         [0042]    The user can now process the service on HT as long as the “leash” is maintained. In the case the leash gets broken (such as U moving away from HT with D) or in any other way, SP will be informed to terminate delivering the service to HT. This information can be communicated either by D or by HT. On receiving this information, the service provider will cease to deliver the service to HT and will require U to authenticate once again (by logging out a user or any embodiment of this action). 
         [0043]    Drawing  3  depicts an embodiment of the website based access system with the addition of a Cloud Service (CS) for authentication and with the service delivered by the SP to the HT directly or via the CS. In the case that the service is delivered to the HT via the CS, the access system comprises of the following 18 steps (many of which are common to the embodiment depicted by Drawing  2  and described above): 
         [0044]    1. U presents credentials to D either using Biometrics ( ) or Pattern unlock or PIN to access D.
       a) If presented with Biometrics, D reads the biometrics.       
 
         [0046]    2. D authenticates U, based on type of credentials/authentication mechanism.
       a) If authenticated D unlocks for U.   b) Else asks U to try again.       
 
         [0049]    3. U requests D to open service S by presenting a biometric credential (U BIOMETRIC ). 
         [0050]    4. D creates BH from U BIOMETRICS . 
         [0051]    5. D decrypts CR STORED  with BH. 
         [0052]    6. U “leashes” himself to Host Terminal (HT) via BT/NFC. (NFC can be used to leash using BT). 
         [0053]    7. HT confirms the leash with a success message. 
         [0054]    8. D asks HT for HT&#39;s Information (port, OS, IP Address, etc.) via D using a secure channel (NFC/BT). 
         [0055]    9. HT provides the Terminal Information to D. 
         [0056]    10. D requests CS to open S by sending the credentials for service CR SERVICE  via a secure channel (MMS, SMS, Wi-Fi) using D. CR SERVICE   ⊂ CR STORED    
         [0057]    11. CS forwards only CR SERVICE  to SP to authenticate. 
         [0058]    12. SP authenticates User based on CR SERVICE    
         [0059]    13. SP authenticates/denies U and provides feedback to CS (which will be forwarded to U) 
         [0060]    14. If SP grants the access
       a. SP provides S to CS   b. CS forwards S to HT.       
 
         [0063]    Otherwise, reject user&#39;s access, and the process is terminated. 
         [0064]    15. U uses S on HT. 
         [0065]    16. D locks itself to prevent misuse. (D can be unlocked via steps 1 and 2) 
         [0066]    17. HT and D monitor physical proximity of U via “leash” established in 6. 
         [0067]    18. If U moves away from HT either
       D requests CS to log off U and terminate connection to HT and CS forwards to SP, to log off U and terminate connection, or   D requests SP to log off U and terminate connection to HT.       
 
         [0070]    Similarly, if the service is provided to the HT directly, the access system comprises of the following 13 steps (many of which are common to the embodiment depicted by Drawing  2  and described above): 
         [0071]    1. U presents credentials to D either using Biometrics ( ) or Pattern unlock or PIN to access D.
       a) If presented with Biometrics, D reads the biometrics.       
 
         [0073]    2. D authenticates U, based on type of credentials/authentication mechanism.
       a) If authenticated D unlocks for U.   b) Else asks U to try again.       
 
         [0076]    3. U requests D to open service S by presenting a biometric credential (U BIOMETRICS ). 
         [0077]    4. D creates BH from U BIOMETRICS . 
         [0078]    5. D decrypts CR STORED  with BH. 
         [0079]    6. U “leashes” himself to Host Terminal (HT) via BT/NFC. (NFC can be used to leash using BT). 
         [0080]    7. HT confirms the leash with a success message. 
         [0081]    8. D asks HT for HT&#39;s Information (port, OS, IP Address, etc.) via D using a secure channel (NFC/BT). 
         [0082]    9. HT provides the Terminal Information to D. 
         [0083]    10. D requests CS to open S by sending the credentials for service CR SERVICE  via a secure channel (MMS, SMS, Wi-Fi) using D. CR SERVICE   ⊂ CR STORED    
         [0084]    11. CS forwards both CRSERVICE and HT information to SP to authenticate. 
         [0085]    12. SP authenticates User based on CR SERVICE    
         [0086]    13. If SP grants the access, SP provides S to HT. Otherwise, reject user&#39;s access, and the process is terminated. 
         [0087]    Drawing  4  depicts the web access system where the credentials used by a service provider to authenticate a user is biometrics. The diagram shows the method of registering the biometrics as a credential with a service provider. In this particular embodiment the method of registering consists of the following 14 steps (many of which are common to the embodiment depicted by Drawing  2  and described above): 
         [0088]    1. U presents credentials to D either using Biometrics (finger print scanner/FaceUnlock) or Pattern unlock or PIN to access D.
       a. If presented with Biometrics, D reads the biometrics.       
 
         [0090]    2. D authenticates U, based on type of credentials/authentication mechanism.
       a. If authenticated D unlocks for U.   b. Else asks U to try again.       
 
         [0093]    3. U requests D to create an account/register for a service S with SP using SP&#39;s app or our app. 
         [0094]    4. D forwards the creation request to SP. 
         [0095]    5. SP replies with requests for a Biometric-Hash (BH), Username and Security Questions. 
         [0096]    6. U gives Username and answers to the Security Questions (SEC_ANSWER) and presents her biometric credential 
         [0097]    7. D reads the user biometric U BIOMETRICS . 
         [0098]    8. D creates a biometric hash BH 
         [0099]    9. D forwards to SP the Username, SEC_ANSWER and also BH. 
         [0100]    10. SP on receiving these values, creates an account for user (which we call service S). 
         [0101]    11. SP confirms account creation to D. 
         [0102]    12. On receiving the confirmation, D stores the salt used to generate the BH. 
         [0103]    13. D confirms account creation to U. 
         [0104]    D now locks itself so that no one can log on. (D can be unlocked by using steps 1 and 2) 
         [0105]    Drawing  5  depicts the embodiment of using biometrics as credentials to access a web service provided by a service provider. In this embodiment, we assume that user has already registered with the service provider her biometric credentials as per the method illustrated in Drawing  4  and described above. The method for using biometrics as authentication credentials consists of the following 18 steps: 
         [0106]    1. U presents credentials to D either using Biometrics (finger print scanner/Face Unlock) or Pattern unlock or PIN to access D.
       a. If presented with Biometrics, D reads the biometrics.       
 
         [0108]    2. D authenticates U, based on type of credentials/authentication mechanism.
       a. If authenticated D unlocks for U.   b. Else asks U to try again. (After may be 3 tries, phone&#39;s contents are purged).       
 
         [0111]    3. U requests D to open service S by presenting a biometric credential (UBIOMETRIC). 
         [0112]    4. D reads user biometric UBIOMETRICS. 
         [0113]    5. D retrieves the salt used in account creation BH. 
         [0114]    6. D generates a biometric hash based on UBIOMETRICS and authenticates U. 
         [0115]    7. U “leashes” himself to Host Terminal (HT) via BT/NFC. (NFC can be used to leash using BT). 
         [0116]    8. HT confirms the leash with a success message. 
         [0117]    9. D asks HT for HT&#39;s Information (port, OS, IP Address, etc.) via D using a secure channel (NFC/BT). 
         [0118]    10. HT provides the Terminal Information to D. 
         [0119]    11. U using D, sends message to SP to open S with credentials (Username and BH) and the Terminal Information to deliver the service to. 
         [0120]    12. SP verifies U via credentials. 
         [0121]    13. SP authenticates/denies U and thus, grants/denies access to S based on result of Step 12. If SP grants the access, SP forwards S to HT. Otherwise, user access is denied and the process is terminated. 
         [0122]    14. SP delivers service to HT. 
         [0123]    15. U uses S on HT. 
         [0124]    16. D locks itself to prevent any misuse. (D can only be unlocked via steps 1 and 2). 
         [0125]    17. HT/D monitors physical proximity of U via “leash” established in 6. 
         [0126]    18. If U moves away from HT with D, either
       D requests SP to log off U and terminate connection to HT or   HT requests SP to log off U and terminate connection to HT.       
 
         [0129]    In the following section we describe the use of the inventions in scenarios involving Cyber-Physical Entities. 
       II. Cyber Physical Entity Access System 
       [0130]    In the embodiments of the CPS entity Access system we will use the following basic definitions and notations in addition to the ones described earlier.
       CPS entity owner&#39;s device (OD).   Reservation request with the reservation starting time, which may either be an instant reservation (if the uses wants to use the CPS entity now) or an advance reservation (if the user wants to use the CPS entity at a later time). It may also contain an finite ending time.       
 
         [0133]    We also describe the general procedure for CPS access system below to highlight the methodology of accessing CPS entities 
       General Procedure: 
       [0134]    User (human) unlocks her smart device. 
         [0135]    The device may communicate with the user agent&#39;s device (if there is such an agent) by sending her BH along with a reservation request via NFC. The Owner could be such an agent for the user, and the Owner&#39;s smart device could be the user agent&#39;s device. 
         [0136]    Either the user device or the user agent&#39;s device will present users&#39; BH and reservation request to the CPS entity or service&#39;s agent, which can be a Reservation System or the owner. NFC is used for communications between the user device, the user agent&#39;s device and the CPS entity, unless they are not in a close range for NFC, in which case, a secure channel (e.g., sms, mms, https, SSL, TLS etc.) is used. 
         [0137]    Reservation is made by the CPS entity (programmed by itself) or by a service agent (which programs the CPS entity). 
         [0138]    When the user presents its smart device to the CPS entity (in a close range via NFC), either the CPS entity or the service&#39;s agent can authenticate the user and grant/deny the service. In the latter case of authentication by the service&#39;s agent, either the CPS entity can send user&#39;s credentials along with its own information, or the user&#39;s smart device can send the CPS entity&#39;s information along with its own credentials, to the service agent for verification. 
         [0139]    All authentication feedback is sent to the CPS entity, based on which the user will either gain or be denied the access. 
         [0140]    Drawing  6  depicts the embodiment of the CPS entity access system using a reservation system. In this embodiment a user makes an instant or advance reservation (with optional payment) through a reservation system using her smart device, and presents her smart device and reservation credentials to the resource when accessing the resource. Authentication can be performed either on the spot by the resource, or by the reservation system. In the latter case, either the resource or the user&#39;s smart device may send to the reservation system the information needed for authentication verification. An owner can also be considered a user herself when the said owner wants to use the entity herself The methodology of accessing the resource in this embodiment consists of the following 14 steps: 
         [0141]    1. U presents credentials to D either using Biometrics (finger print scanner/Faceunlock, etc.) or Pattern unlock to access D. 
         [0142]    2. D reads the input and authenticates U, based on type of credentials/authentication mechanism.
       a. If authenticated D unlocks for U.   b. Else asks U to try again. (After a few tries, phone&#39;s contents are purged).       
 
         [0145]    3. U selects the resource R and enters the desired access time (either instant or advance reservation) and her Biometric. 
         [0146]    4. D reads U&#39;s biometric (U BIOMETRICS ). 
         [0147]    5. D creates a BH based on U BIOMETRICS . 
         [0148]    6. D sends BH and reservation request information to RS. 
         [0149]    7. RS enquires R of service availability. 
         [0150]    If there is not availability of service from R the process terminates 
         [0151]    8. R confirms availability to RS. 
         [0152]    9. Payment scenario:
       i. RS sends D the reservation cost details.   ii. D presents U the cost details.   iii. U enters payment method and authorizes transaction for payment.   iv. D sends RS payment details.   v. RS validates U&#39;s payment information.       
 
         [0158]    If RS cannot validate U&#39;s payment information, the process is terminated (and U is informed via D). 
         [0159]    10. RS makes the reservation and confirms to U via D the reservation. 
         [0160]    11. U via D requests immediate access to the reserved resource. 
         [0161]    12. D generates BH (the same as that generated in step 5) after reading biometric input from U (U BIOMETRICs ) and sends it to the resource via NFC to requests access. 
         [0162]    13. On the Spot Authentication: R authenticates U by using the supplied BH and other reservation information (such as the reserved access time). 
         [0163]    13. (Alternative) Backend Authentication
       a. Either Resource to Reservation System Authentication: R sends the supplied BH, along with other reservation information, to RS.   Or User to Reservation System Authentication: (i). D requests R for its information,   (ii). R provides details to D, and (iii). D provides Resource details, along with its BH and other reservation information, to RS.   b. RS authenticates U based on the information provided (including the reserved access time).   c. RS provides R with feedback       
 
         [0169]    14. Based on the authentication result from the previous steps, the resource either grants or denies access to the user. 
         [0170]    Drawing  7  depicts the second embodiment of the CPS entity system where the user reserves a resource via the owner (a human) of the resource. The main differences in this embodiment against the previous embodiment are that the user makes the reservation using her smart device through an owner who is also using her smart device and that the authentication is performed on the spot by the resource without involving the owner or the owner&#39;s agent. This embodiment also allows the owner to gain access to the resource using the on-the-spot authentication when the owner acts as the resource. The methodology involved in this embodiment consists of the following 14 steps: 
         [0171]    1. U presents credentials to D either using Biometrics (finger print scanner/Face unlock, etc.) or Pattern unlock to access D. 
         [0172]    2. D reads the input and authenticates U, based on type of credentials/authentication mechanism.
       a. If authenticated D unlocks for U.   b. Else asks U to try again. (After a few tries, phone&#39;s contents are purged).       
 
         [0175]    3. U selects the resource R and enters the desired access time (either instant or advance reservation) and her Biometric. 
         [0176]    4. D reads U&#39;s biometric (UBIOMETRICS). 
         [0177]    5. D creates a BH based on UBIOMETRICS. 
         [0178]    6. D sends BH and reservation request information to OD. 
         [0179]    7. OD displays U&#39;s information to O and requests for authorization. 
         [0180]    8. If O agrees to consider the reservation, O will use OD to take the (optional) payment (as in 
         [0181]    Step 9 in the first embodiment of the CPS entity access system, refer to Drawing  7 ). 
         [0182]    If O does not approve the reservation request, the process is terminated (and U is informed via D). 
         [0183]    9. If O authorizes the reservation by U, O will use OD to send U&#39;s reservation request to R, and makes the reservation. 
         [0184]    10. Reservation confirmation using devices.
       a. OD confirms to O the reservation.   b. OD also confirms to U via D the reservation. Alternately, O confirms to U in person (orally, in writing, or any other means).       
 
         [0187]    11. U via D requests immediate access to the reserved resource. 
         [0188]    12. D generates BH (the same as that generated in step 5) after reading biometric input from U (UBIOMETRICs) and sends it to the resource via NFC to requests access. 
         [0189]    13. On the Spot Authentication: R authenticates U by using the supplied BH and other reservation information (such as the reserved access time). 
         [0190]    14. Based on the authentication result from the previous steps, the resource either grants or denies access to the user. 
         [0191]    Drawing  8  depicts the third embodiment of the CPS entity access system where the user wants to reserve or access a resource via an owner who uses a reservation system. In this particular embodiment, the main difference from the previous two embodiments are that the user makes a reservation through an owner and the owner&#39;s smart device, which in turn interfaces with the reservation system. The methodology of accessing the CPS entity in this embodiment consists of the following 15 steps: 
         [0192]    1. U presents credentials to D either using Biometrics (finger print scanner/Face unlock, etc.) or Pattern unlock to access D. 
         [0193]    2. D reads the input and authenticates U, based on type of credentials/authentication mechanism.
       a. If authenticated D unlocks for U.   b. Else asks U to try again. (After a few tries, phone&#39;s contents are purged).       
 
         [0196]    3. U selects the resource R and enters the desired access time (either instant or advance reservation) and her Biometric. 
         [0197]    4. D reads U&#39;s biometric (U BIOMETRICS ). 
         [0198]    5. D creates a BH based on U BIOMETRICS . 
         [0199]    6. D sends BH and reservation request information to OD. 
         [0200]    7. OD displays U&#39;s information to O and requests for authorization. 
         [0201]    8. If O authorizes the reservation, O will use OD to send U&#39;s reservation request to RS. 
         [0202]    Otherwise, the process terminates (and the U is informed). 
         [0203]    9. RS will perform the reservation and optional payment operations as in Steps 7 to 9 in first embodiment of CPS entity Access System, refer to Drawing  6 . 
         [0204]    10. RS confirms to O the result of the reservation via OD. If the reservation failed, the process will be terminated (and U is informed). 
         [0205]    11. User is confirmed the reservation either by D (via OD) or by O in person. 
         [0206]    12. U via D requests immediate access to the reserved resource. 
         [0207]    13. D generates BH (the same as that generated in step 5) after reading biometric input from U (U BIOMETRICS ) and sends it to the resource via NFC to requests access. 
         [0208]    14. On the Spot Authentication: R authenticates U by using the supplied BH and other reservation information (such as the reserved access time). 
         [0209]    14. (Alternative) Backend Authentication
       d. Either Resource to Reservation System Authentication: R sends the supplied BH, along with other reservation information, to RS.   Or User to Reservation System Authentication: (i). D requests R for its information, (ii). R provides details to D, and (iii). D provides Resource details, along with its BH and other reservation information, to RS.   e. RS authenticates U based on the information provided (including the reserved access time).   f. RS provides R with feedback       
 
         [0214]    15. Based on the authentication result from the previous steps, the resource either grants or denies access to the user. 
       REFERENCES 
       [0215]    [1] A. Adams, M. Sasse, and P. Lunt, “Making passwords secure and usable.” People and Computers, pp. 1-20,1997. 
         [0216]    [2] P. Inglesant and M. Sasse, “The true cost of unusable password policies: password use in the wild.” in Proceedings of the 28th international Conf. on Human factors in computing systems. ACM, 2010, pp. 383-392. 
         [0217]    [3] R. Shay and E. Bertino, “A comprehensive simulation tool for the analysis of password policies.” International Journal of Information Security, vol. 8, no. 4, pp. 275-289,2009. 
         [0218]    [4] J. Stanton, K. Stam, P. Mastrangelo, and J. Jolton, “Analysis of end user security behaviors.” Computers &amp; Security, vol. 24, no. 2, pp. 124-133,2005. 
         [0219]    [5] S. Komanduri, R. Shay, P. Kelley, M. Mazurek, L. Bauer, N. Christin, L. Cranor, and S. Egelman, “Of passwords and people: Measuring the effect of password-composition policies.” in Proc. of the 2011 annual Conf. on Human factors in computing systems. ACM, 2011, pp. 2595-2604. 
         [0220]    [6] A. Brown, E. Bracken, S. Zoccoli, and K. Douglas, “Generating and remembering passwords.” Applied Cognitive Psychology, vol. 18, no. 6, pp. 641-651,2004. 
         [0221]    [7] B. Ives, K. Walsh, and H. Schneider, “The domino effect of password reuse.” Communications of the ACM, vol. 47, no. 4, pp. 75-78,2004. 
         [0222]    [8] D. Feldmeier and P. Karn, “Unix password security-ten years later.” In Advances in Cryptology CRYPTO89 Proc. Springer, 1990, pp. 44-63. 
         [0223]    [9] Y. Zhang, F. Monrose, and M. K. Reiter, “The security of modern password expiration: an algorithmic framework and empirical analysis.” in Proceedings of the 17th ACM Conf. on Computer and communications security, ser. CCS &#39;10. New York, NY, USA: ACM, 2010, pp. 176-186. 
         [0224]    [10] B. Laxton, K. Wang, and S. Savage, “Reconsidering physical key secrecy: Teleduplication via optical decoding.” in Proceedings of the 15th ACM Conf. on Computer and communications security. ACM, 2008, pp. 469-478. 
         [0225]    [11] M. Backes, M. Durmuth, and D. Unruh, “Compromising reflections-or how to read lcd monitors around the corner.” in Security and Privacy, 2008. SP 2008. IEEE Symposium on. IEEE, 2008, pp. 158-169. 
         [0226]    [12] F. Tari, A. Ozok, and S. Holden, “A comparison of perceived and real shoulder-surfing risks between alphanumeric and graphical passwords.” in Proceedings of the second symposium on Usable privacy and security. ACM, 2006, pp. 56-66. 
         [0227]    [13] M. Sasse, S. Brostoff, and D. Weirich, “Transforming the weakest link a human/computer interaction approach to usable and effective security.” BT technology journal, vol. 19, no. 3, pp. 122-131,2001.