BACKGROUND

[0001] Single-function imaging devices, such as scanners, printers, facsimile devices and photocopying devices are increasingly becoming mufti- function devices. For example, a printer implemented as a single-function imaging device may receive a print command from a user and execute the print command to render content on a medium. However, a multi-function printer may incorporate, along with its capability to print content, functionality of a scanner and may accept a scan command from a user to enable generation of an electronic copy of a document in another example, a scanner may also create a physical copy of a document thereby exhibiting functionalities of a photocopying device.

BRIEF DESCRIPTION OF FIGURES

[00023 The following detailed description references foe drawings, wherein:

[0003] Figure 1 illustrates a secure scanning system using an imaging device implemented in a network environment, in accordance with an example of the present subject matter;

[00043 Figure 2 illustrates an imaging device, in accordance with an example of toe present subject matter;

[0005] Figure 3 illustrates an imaging device, in accordance with an example of toe present subject matter;

[00063 Figure 4 illustrates a method for obtaining a scanned document from an imaging device, in accordance with an example of the present subject matter;

[0007] Figure 5 illustrates a method for scanning a document by an imaging device, in accordance with an example of toe present subject matter; and [0008] Figure 6 illustrates a computing environment implementing a non- transitory computer-readable medium for securing access to a document scanned by an imaging device, according to an example of foe present subject matter.

DETAILED DESCRIPTION

[0009] A multi-function imaging device, is a device incorporating multiple functionalities, such as that of a printer, a scanner, a fax and a photocopier. On foe other hand, a single-function imaging device may act for example, as a scanner alone: Multi-function imaging devices and single-function imaging devices are referred to as imaging devices herein.

[0010] While implementing multiple functionalities in the imaging devices enhances users' experience, such an implementation may also pose various data security related threats. For instance, a document provided by a user to an imaging device solely for the purposes of scanning, may be maliciously photocopied, for example, by a rogue operator of foe imaging device.

[0011] Further, the imaging devices may be implemented in a network environment where multiple users connect to an Imaging device over foe network to use functionalities of foe imaging device. Implementing foe imaging devices in foe network environment, enhances accessibility of foe imaging devices by foe users and in turn enhances users’ experience. For example, a user may provide a command to foe imaging device to print a document, through any user device connected to the network, for example, from a remote location. However, such a network implementation may often further amplify data security related threats associated with foe imaging devices.

[0012] For instance, consider a situation where an imaging device Is used for scan-to-email operation for scanning a document and sending foe scanned data to an email address. To send the scanned data to foe email address, a user may indicate foe email address to foe imaging device, for example, by selecting the email address from a list of email addresses registered with foe imaging device. In such cases, it is possible, that the user or a rogue operator may, inadvertently or conspicuously, provide a wrong email address, thus resulting in unauthorized dissemination of die scanned data. Furthermore, the scanned data may be disseminated to multiple «nail addresses. Thus, generally, scam operations by imaging devices may be vulnerable to date security issues.

[0013] According to an example of toe present subject matter, techniques to secure scan operations by imaging devices implemented in a network environment, for preventing unauthorized dissemination of scanned data, is described. Example techniques described herein enable the imaging devices to provide toe scanned data to an authorized user who has requested the scan operation.

[0014] According to an example of the present subject matter, a secure scanning system using an imaging device is implemented in a network environment. According to die present subject matter, a user may send a scan request to die imaging device. The scan request comprises a contact identifier of the user, tn an example, the contact identifier may be an email address of the user. The imaging device receives the scan request and creates a proxy scan job corresponding to the scan request. The imaging device also generates a password for the proxy scan job and sends die password to die contact identifier of the user. The imaging device executes die proxy scan job to scan a document when the password is provided to the imaging device as a user input. The scanned document is thereafter sent to the contact identifier.

[0015] Thus, according to the present subject matter, the imaging device is to perform scan operations based on a scan request associated with a contact identifier of the user and provide the scanned document to the contact identifier, thus eliminating possibility of sharing the scanned document with an unauthorized user.

[0016] The above techniques are further described with reference to figure 1 to Figure 6. It should be noted that toe description and the figures merely illustrate toe principles of toe present subject matter along with examples described herein and should not be construed as a limitation to the present subject matter. It is thus understood that various arrangements may be devised that, although not explicitly described or shown herein, embody tile principles of the present subject matter. Moreover, all statements herein retiting principles, aspects, and implementations of the present subject matter, as well as specific examples thereof, are intended to encompass equivalents thereof.

[0017] Figure 1 shows a secure scanning system 100 comprising an imaging device 102 and a plurality of user devices 104-1 , 104-2, and 104-3 implemented in a network environment according to an example of the present subject matter. Examples of imaging device 102 indude scanners, digital senders, single function printer (SFP), multi-function printer (MFP), photocopiers, etc. In an example, a plurality of imaging device 102 may be present in the network environment, however, for the simplicity, a single imaging device 102 is shown in foe figure.

[0018] The imaging device 102 may be accessed by foe plurality of user devices 104-1, 104-2, and 104-3. Examples of foe user devices 104-1, 104-2, 104-3 may indude, but are not limited to, electronic devices, such as desktop computers, laptops, smartphones, personal digital assistants (PDAs), and tablets. The plurality of user devices 104-1, 104-2, and 104-3, collectively referred to as user devices 104, may be used to provide a scan request to foe imaging device 102 for scanning a document. In an example, a user device, such as the user device 104-1 may be coupled to a plurality of imaging devices and the user may indicate, in foe scan request, foe imaging device to which he desires to send the scan request.

[0019] In an example, foe scan recjuest from a user device, siuch as the user device 104-1 may be provided to foe imaging device 102 via a server 106. For example, the user device 104-1 may be a mobile device such as a smartphone or tablets not incorporating a scan driver for generating the scan request in a format that would be understandable or supported by foe imaging device 102. In such example implementations, foe user device 104-1 may communicate foe scan request to the imagine device 102 via the server 106.

[0020] In an example, the server 106 may be any server for managing foe multiple imaging devices in foe network environment. For example, the server may manage the dissemination of a scan request to a designated imaging device. The server 106 may be implemented as a computing device, including, for example, a workstation, a mainframe computer, a desktop, a personal computer, a notebook, a portable computer, and a laptop. Further, in one example, toe server 106 may be a distributed system in which different computing devices may host toe hardware or software components of toe server

106.

[0021] In an example, toe user device 104-1 may provide tine scan request to the server 106 over a network 108 which may in turn transmit toe scan request to the imaging device 102 over the second network 108. In an example, the network 108 may be a single network or a combination of multiple networks and may use a variety of different communication protocols. The network 108 may be a wireless or a wired network, or a combination thereof. Examples of such individual networks include, but are not limited to, Global System for Mobile Communication (GSM) network, Universal Mobile telecommunications System (UMTS) network, Persona! Communications Service (PCS) network. Time Division Multiple Access (TDMA) network, Code Division Multiple Access (CDMA) network, Next Generation Network (NON), Public Switched Telephone Network (PSTN). Depending on toe technology, toe network 108 includes various network entities, such as gateways, routers; however, such details have been omitted for sake of brevity of the present description.

[0022] The server 106 modifies toe scan request received from the user device 104-1 in a format supported by the imaging device 102 and thereafter transmits the scan request to toe imaging device 102. In an example, when there is plurality of imaging devices present in toe network environment, toe server 106 may identify, based on a device identifier included in the scan request received from the user device 104-1, the imaging device 102 to which toe scan request is to be transmitted. Further, in an example, the server 106 may decide, based on toe pending tasks with each of toe imaging devices in toe network, an imaging device to which the scan request should be directed. For example, the server 106 may direct toe scan request to an imaging device which has relatively less tasks pending in its queue in another example, the server 106 may direct the scan request to an imaging device which is nearest to the contact identifier of the user.

[0023] The scan request may, for example, be understood as a command provided to the imaging device 102 for scanning a document comprising a tingle or multiple pages. The scan request may comprise instructions relating to the scanning operations. The instructions may indicate to the imaging device 102 a resolution for scanning the document, a mode, such as monotime or color mode of scanning and so on.

[0024] Further, the scan request comprises a contact identifier associated with a user of the user device 104-1. The contact identifier associated with foe user may be an «nail address, a mobile number, a fax number or any dfoer contact number or address which may be used to communicate with the user.

[0025] Upon receiving the scan request, the imaging device 102 creates a proxy scan job corresponding to the scan request. The proxy scan job may be understood as an executable task which when executed performs a scanning operation on foe imaging device 102. The proxy scan job is stored in foe imaging device 102 and may be executed and may be queued with the pending tasks of the imaging device 102. The proxy scan job may be executed at a later point of time when initiated by a user. Further, the imaging device 102 generates a password corresponding to the proxy scan job.

[0026] The imaging device 102 transmits the password to the contact identifier of the user. The proxy scan job, stored in foe imaging device 102, may be executed by a scan engine 112 of the imaging device 102 when foe password is provided to the imaging device 102 as a user input. Execution of foe proxy scan job causes a document, kept on a scanner bed of foe imaging device 102, to be scanned. The scanned document is thereafter transmitted to foe contact identifier via foe server 106 over the network 108.

[0027] Hius, according to the present subject matter a scanning operation is executed for foe scan request received by foe imaging device 102. In one example, scan requests received from authorized sources alone may be processed. For example, a list of authorized contact identifiers may be defined for the imaging device 102. A scan request associated with a contact identifier that is not present in the list of authorized contact identifier may be discarded by the imaging device 102 and may not be processed further for creation of a corresponding proxy scan job.

[0028] Further, the imaging device 102 executes foe proxy scan job upon receiving the password corresponding to the scan request This allows users flexibility for controlling execution of scan jobs. For instance, in cases where a user is remotely located, and is unable to access the imaging device 102 to execute the proxy scan job, he may share the password with another user who can access the imaging device. The other user may execute the proxy scan job on the behalf of the user by entering the password into the imaging device 102. As a result of such an execution, the scan data generated corresponding to foe scanned document, interchangeably referred to as scanned document herein, is transmitted to the user initiating foe scan request.

[0029] Since foe imaging device 102 sends the scanned date to foe contact identifier from which the scan request is received, it would not be possible for foe person who may have entered foe password or any other unauthorized person to receive the scanned data. Further, since the user does not specify an address, such as «nail address to foe imaging device 102 for delivering the scanned document and scanned document is transmitted to the contact identifier received with foe scan request, errors due to inadvertently providing incorrect email addresses to the imaging device 102 are eliminated.

[0030] Figure 2 shows foe imaging device 102, according to an example of foe present subject matter.

[0031] According to an example of the present subject matter, foe imaging device 102 comprises a communication engine 202 and the scan engine 204. The scan engine 204 may be similar to the scan engine 112. The communication engine 202 receives a scan request from a user device, such as the user device 104-1. As mentioned previously, the scan request comprises a user identifier of foe user. The communication engine 202 creates a proxy scan job corresponding to the scan request. In an example, foe proxy scan job is assigned a scan job identifier. The scan job identifier may, in an example, uniquely identify each of the multiple proxy scan jobs created corresponding to the multiple scan requests received by the communication engine 202 from the user device 104-1.

[0032] Further to creation of the proxy scan job, the communication engine 202 generates a password associated with the scan job identifier. The communication engine 202 provides the scan job identifier to the contact identifier included in the scan request. The communication engine 202 further causes the password to be sent, either together with the scan job identifier or at different instance of time, to the contact identifier included in the scan request.

[0033] The scan engine 112 of the imaging device 102 is to execute toe proxy scan job to scan a document when the password is received as a user input. In an example, toe user may select the proxy scan job based cm toe scan job identifier and may provide the corresponding password to toe imaging device 102, for instance, when prompted by the imaging device 102 based on the user's action of selecting the proxy scan job based on the scan job identifier. After the scan operation is completed, the scan engine 204 causes the scanned document to be transmitted to toe contact identifier.

[0034] In another example implementation, while toe communication engine 202 may create a proxy scan job corresponding to toe scan request and assign a scan job identifier at the time of receipt of the scan request, toe communication engine 202 may delay toe generation of toe password corresponding to toe scan job. Alternatively, in an example, the password may be generated upon toe receipt of toe scan request, however, toe password may be temporarily stored such that the transmission of toe password may be delayed. As apparent, in such implementations, toe scan job identifier alone may be transmitted to the contact identifier included in toe scan request. Subsequently, at a later instance, when a user selects the scan job for execution, for instance, based on the scan job identifier assigned to toe job, toe password may be transmitted, in response to the selection of toe scan job, to the contact identifier included in the scan request.

[0035] To explain in other words, the user may select the proxy scan job through a user interface of toe imaging device 102 to indicate to toe imaging dewoe 102 that the proxy scan job is to be executed in an implementation, the scan engine 112 of the imaging device 102 may detect the selection of the proxy scan job by the user and may trigger the communication engine 202. In another example, the communication engine 202 may itself detect the selection of the proxy scan job by the user. Based on the selected proxy scan job, in an example, the communication engine 202 generates a password and transmits the same to the contact identifier associated with tine scan request that resulted in creation of the selected proxy scan job. In another example, if the password was generated at the time of receipt of the scan request and stored for delayed transmission, the same may be retrieved by the communication engine 202 and transmitted to the contact identifier.

[0036] Thereafter, as mentioned above, toe scan engine 112 of toe imaging device 102 executes the proxy scan job to scan a document when the password transmitted to toe contact identifier is provided to the imaging device 102 as an input and causes toe scanned document to be transmitted to toe contact identifier.

[0037] The scanned document is thus transmitted to the contact identifier which was received with the scan request. Thus, according to the present subject matter, to receive the scanned document, the process of configuring an email address fey the imaging device 102 to deliver the scan data to that email address is eliminated. According to the present subject matter, the scanned document is sent to the contact identifier which is received with toe scan request. Thus, additional process of configuring or providing the email address as well as the errors that may result from providing a wrong or unauthorized email for receiving toe scanned document are eliminated.

[0038] Additionally, toe above described implementations also provide for delayed generation and transmission of passwords thereby enabling users to execute proxy scan jobs, corresponding to scan requests that may have been created at a prior instance, without having the users to securely maintain or store toe password. The users have the flexibility to receive a password, for example, at an instance when a document to be scanned has been positioned on a scanning bed of the imaging device 102 and execution of the proxy scan job is triggered and thus have enhanced user experience.

[0039] Figures 3 illustrates an imaging device 102, in accordance with another example of the present subject matter.

[0040] The imaging device 102, among other things, indudes and a memory 302, interface(s) 304, and engine(s) 306. The memory 302 may indude any computer-readable medium including, for example, volatile memory (e.g., RAM), and/or non-volatile memory (e.g., EPROM, flash memory, etc.). ^" The interface 304 may include a variety of software and hardware interfaces that allow tiie imaging device 102 to interact with other devices, such as tee user devices 104-1, 104-2, and 104-3 or other input/output (I/O) devices teat may be used to provide inputs, such as, passwords, selection of proxy scan job to imaging device 102.

[0041] The engine(s) 306 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement certain functionalities of tee engine(s) 306, such as creating proxy scan jobs, transmitting passwords and executing instructions in response to receiving tee password. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for tee engine(s) 306 may be processor executable instructions stored on a non-transitory machine-readable storage medium and the hardware for tee engine(s) 306 may include a processing resource (for example, implemented as either a single processor or a combination of multiple processors), to execute such instructions. In the present examples, tee machine-readable storage medium may store instructions that, when executed by tee processing resource, implement engine(s) 306.

[0042] In such examples, tee imaging device 102 may include tee machine-readable storage medium storing tee instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the imaging device 102 and the processing resource. In other examples, engine(s) 306 may be implemented by electronic circuitry. The engine(s) 306 may indude a communication engine 308, a scan engine 310, a print engine 312, and an authentication engine 314. Hie communication engine 308 may be simitar to the communication engine 202 and the scan engine 310 may be similar to the scan engine 112, In an example, the engine(s) 306 may also comprise other engine(s) 306 that supplement functions of the image imaging device 102.

[00433 Data 318 serves, amongst other things, as a repository for storing data mat may be fetched, processed, received, or generated by the engine(s) 306. The data 318 comprises other data 320 corresponding to the other enginefs) 306. In the illustrated example, the data 318 of toe imaging device 102 also comprises communication data 322, scan data 324, and proxy scan job data 326. The other data 320 may store toe data pertaining to the other engine(s) 306.

[0044] In operation, the communication engine 308 receives a scan request from a server, such as the server 106. In an example, the scan request received by the communication engine 308 may be an email from the server 106. As mentioned previously, toe scan request, i.e., the email from the server 106 in toe present example, comprises a contact identifier of a user initiating the scan request. Again, as mentioned previously, in an example, the contact identifier may be the email address of the user. The contact identifier may be stored in the communication data 322.

[0045] In an example, the scan request is an email directed to an email address associated with the scan engine 310 of the imaging device 102. In an example, the imaging device 102 may be a multifunction peripheral (MFP) having different email addresses associated with each of its peripherals, such as a scanner peripheral or the scan engine 310 and a printer peripheral or print engine 312. For example, the imaging device 102 may have an email address, for example, print123@domainname.com for the printer peripheral or the print engine 312. A user may send a print request in the form of an «mail to the email address of the print engine 312. Further, toe imaging device 102 may have another email address, for example, scan123@domainname.com for the scan engine 310. To send a scan request to the imaging device 102, a user may send an email to the email address of the scan engine 310 of the imaging device 102. Thus, the imaging device 102 may determine a request received as an «mail to be a scan request or a print request based on email address at which the request is received.

[0046] In another example, a common email address, say imaainodeviceiD@dcmainname.com may be used by the different peripheral of the imaging device 102 for receiving requests relating to different functionalities of the imaging device 102. In an example, a user may send a request for a printing operation or a scanning operation on the email address of the imaging device 102. In an example, a scan request may be an email directed to the email, imaainadevicelD@dcNmanname.com. of the imaging device 102. According to the present subject matter, the «nail may indude an indicator which is indicative of a scan job. For example, the email may comprise a read receipt as an indicator. The read receipt may be detected by the communication engine 308 to determine that the email is a scan request to- performing a scanning operation.

[004h The indicator, i.e., the read receipt in the present example, maybe used to distinguish a scan request from other types of requests that may be received by the imaging device 102 without having to create a dedicated «nail addresses for the scanner peripheral or the scan engine 310 of the imaging device 102. Accordingly, an email with a read receipt may be construed as a scan request as opposed to an email without a read receipt that may be construed as a print request, for instance.

[0048] Once the scan request is received at the imaging device 102, the authentication engine 314 may determine, based on the contact identifier associated with the scan request, whether the imaging device 102 is authorized to accept the scan request. As explained previously, the scan request may be an email from the server 106 and may comprise a contact identifier, such as an email address or contact number of a user initiating the scan request. The imaging device 102 may be authorized to accept the scan requests from some contact identifiers alone and may thus make a determination if the instant scan request may be accepted or not

[0049] In an example implementation, the imaging device 102 may store a list of authorized contact identifiers. In an example, toe list of authorized contact identifiers may be stored in toe communication data 322. The authentication engine 314 may compare the contact identifier received with toe scan request with toe list of authorized contact identifiers. As explained earlier, the contact identifier received with the scan request may also be stored in the communication data 322. To determine If the contact identifier is authorized for sending the scan request, the authentication engine 314 may retrieve toe contact identifier from toe communication data 322 and may compare toe retrieved contact identifier with the list of authorized contact identifiers, if toe retrieved contact identifier matches with a contact identifier in toe list of authorized contact identifiers, the authentication engine 314 may determine that the imaging device 102 is authorized to accept the scan request.

[0050] Considering an example where toe contact identifier received with the scan request is an email address, xvz@domainname com toe authentication engine 314 may determine whether toe email address, x¾z@domainname,com, is present in the list of authorized contact identifiers. If the email address, x vz@domainnname .com . received with the scan request, matches with an email address in the list of authorized contact identifiers, toe authentication engine 314 may determine that the imaging device 102 is authorized to accept toe scan request. If toe email address, xvz@domainnname.com. received with the scan request, does not match with an email address in toe list of authorized contact identifiers, the authentication engine 314 may determine that toe imaging device 102 is not authorized to accept the scan request and the scan request may be discarded, in an example, the list of authorized contact identifiers may be defined based on toe domain name. Referring to the above example, if a domain name, such as domainname.com is authorized, a scan request originating from an email address associated with such an authorized domain name is acceptable. [0051] When ¾ is determined that the scan request is acceptable or, in other words, the imaging device 102 is authorized to cater to the scan request the communication engine 308 creates a proxy scan job corresponding to die scan request The proxy scan job is stored in the proxy scan job data 326. The proxy scan job is an executable command which when executed performs a scanning operation to scan a document that may be placed on a scanning bed to the imaging device 102.

[0052] Further, communication engine 308 may assign a scan job identifier to the proxy scan job. For example, the communication engine 308 may receive die scan request from a contact identifier, xyz@domainname.oom and after it is determined that the contact identifier is authorized, die communication engine 308 may create a proxy scan job. Further, die communication engine 308 may assign a scan job identifier,‘xyz-scan ^* to die proxy scan job. The scan job identifier‘xyz-scan’ may be saved in die proxy scan job data 326.

[0053] After the proxy scan job is created, the communication engine 308 generates a password associated with the scan job identifier. The password may be composed of numerals, characters, special characters or a combination thereof. In an example, the password may also be stored in proxy scan job data 326 in association with the corresponding proxy scan job. The communication engine 308 further sends the password and the scan job identifier to the contact identifier, for example via the interface^) 304 of the imaging device 102. For example, where the contact identifier is an email address, the password and die scan job identifier are transmitted to the email address, likewise, if die contact identifier is a mobile number the password and the scan job identifier may be transmitted to the mobile number and so on.

[0054] For example, considering the above example, the communication engine 308 may generate a password xyz@123' for the scan job identifier‘xyz- scan ^* . The communication engine 308 may send the password, ^* xyz@123‘ and the scan job identifier 'xyz-scan’ to the contact identifier of the user. The user may access the password, ^< xyz@123’ _> and the scan job k!entifier,‘xyz-scan’, on his contact identifier.

[0055] The imaging device 102 may receive multiple scan requests and may create a proxy scan job corresponding to each scan request. The multiple proxy scan jobs may be queued by the imaging device 102 for execution. For example, the imaging device 102 may display foe proxy scan jobs, for example, as a list or a queue. In an example, in the displayed list, the proxy scan jobs may be listed against their corresponding contact identifier. In another example, the imaging device 102 may display the scan job identifiers created for each of the multiple scan requests received at the imaging device 102, such that a proxy scan job may be selected based on its corresponding scan job identifier for execution.

[0056] In an example, for executing a scan job, fire user may select the proxy scan job, for example, based on the corresponding scan job identifier that is communicated to the user via his contact identifier. In an example, the scan engine 310 of the imaging device 102 may allow selection of a proxy scan job based on the corresponding proxy scan job identifier. In an example, any other user, on the behest of file user, may also select the scan job identifier. For example, when file user is at a remote location such that he cannot access the imaging device 102, file user may ask the other user, who may be in the vicinity of the imaging device 102, to execute the proxy scan job on behalf of the user. In such cases, the user may share the scan job identifier and the password, which he has received on his contact identifier as a resuit of initiation of the scan request, with the other user.

[0057] Upon selection of the proxy scan job identifier, the imaging device 102 may prompt the user to provide the password. The user may provide the password for the corresponding scan job identifier to the imaging device 102. The authentication engine 314 may receive the password and may thereafter authenticate the received password. The received password is authenticated if it is same as the password sent to the contact identifier for the selected scan job identifier. The authentication engine 314 compares the received password with the password stored in the proxy scan job data 326 for the selected scan job identifier, if foe received password matches with foe password stored in foe proxy scan job data 326 for foe selected scan job identifier, the authentication is successful,

[0058] In case when foe authentication is unsuccessful, due to incorrect password or incorrect combination of selected scan job identifier and foe corresponding password, foe scan engine 310 does not execute foe proxy scan job corresponding to the selected scan job identifier. However, if foe authentication engine 314 successfully authenticates the password, the scan engine 310 executes the proxy scan job to scan a document kept on a scanner bed of the imaging device 102. In an example, foe user may keep foe document on the scanner bed prior to selecting the scan job identifier and then providing the password. The scanned document may be stored in the scan data 324. The scan engine 310 may retrieve the scanned document stored to the scan data 324 and transmit the same to foe contact identifier of foe user. In an example, once the scan engine 310 has transmitted the scanned document, the scanned document stored in the scan data 324 is deleted.

[0059] In an example, the imaging device 102 may comprise a print engine 312 to print the scanned document upon being instructed by the user by way of a print command or a command to generate a photocopy of foe document being scanned. Upon user's command, foe print engine 312 may retrieve the scanned document from the scan data 324 and may thereafter print the scanned document. While printing the scanned document, foe print engine 312 may insert an indication of foe contact identifier, received with the scan request, in the printed document in an example, foe indication may be included in the footnote of the document. In an example, considering that the scan request comprises a contact identifier, abc@domainname.com. while printing of the scanned document generated corresponding to the scan request the print engine 312 may include a footnote:‘scanned document transmitted to abc@ domainname.com’ in foe printed document. [0060] in an example* including the indication of contact identifier in the printed document may alert a user about any scanning operation which may have been performed on a document being photocopied. Consider a scenario where an above described imaging device is being used as a photocopier, by an operator, for photocopying documents of customers. For photocopying, toe imaging device scans toe document and thereafter prints it. A customer may provide toe operator, a document for photocopying. The operator may, by using toe method as described above, execute a proxy scan job initiated by him in parallel to the photocopying operation and may transmit the scanned toe document to a contact identifier, such as his email address. According to toe present subject matter, when the operator performs the scan operation along with the photocopying, an indication is included in the printed document which indicates that a scanning operation has been performed on the document and the scanned data is has been transmitted to third party. This may alert toe customer that toe operator is involved in malpractices.

[0061] Figure 4 illustrates a method 400 for obtaining a scanned document from an imaging device, according to an example of the present subject matter. Although toe method 400 and may be implemented in a variety of user devices, for the ease of explanation, the present description of toe example method 400 is provided in reference to toe above-described user device 104-1 implemented in toe secure scanning system implemented in toe network environment.

[0062] The order in which toe method 400 is described is not intended to be construed as a limitation, and any number of toe described method blocks may be combined in any order to implement the method 400, or an alternative method.

[0063] It may be understood that blocks of the method 400 may be performed by the user device 104-1. The blocks of toe method 400 may be executed based on instructions stored in a non-transitory computer-readable medium, as will be readily understood. The non-transitory computer-readable medium may indude, for example, digital memories, magnetic storage media, such as magnetic disks and magnetic tapes _» hard drives, or optically readable digital data storage media.

[0064] Referring to Figure 4, The method starts at block 402 and proceeds to block 404. At block 404, a user device, such as toe user device 104-1 sends a scan request to a sever, such as the server 106. As explained earlier, the scan request can be understood as a command for scanning a document. The scan request may include details like number of pages for scanning, single side/double side scanning, monotone or colored scanning, image quality, such as high image resolution or medium image resolution and so on. The scan request comprises a contact identifier, such as email address, a mobile number of a user. Through the server 106, the scan request is eventually transmitted to an imaging device, such as toe imaging device 102. As explained in the foregoing description, based on receipt of toe scan request toe imaging device 102 generates a password and transmits the same to toe contact identifier.

[0065] At block 406, the user device 104-1 receives a password associated with the scan request, in response to sending the scan request. At block 408, the user device 104-1 receives scan data corresponding to the scan request upon the password being provided to the imaging device 102. For receiving the scan data, the password may be manually fed into the imaging device 102, which performs toe scanning operation upon verification of toe password. The method, thereafter, stops at block 410.

[0066] Thus, according to the present subject matter the scanned document is delivered to the contact identifier received with the scan request. This makes tiie Scanning operation secure from any unauthorized tapping of the scanned document.

Eqqbh Figure 5 illustrates a method 500 tor scanning a document by an imaging device, according to an example of the present subject matter. Although toe method 500 and may be implemented in a variety of imaging device, for toe ease of explanation, toe present description of the example method 500 to scan the document is provided in reference to tile above- described imaging device 102.

[0068] The order in which the method 500 is described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method 500, or an alternative method.

[0069] It may be understood that Modes of the method 500 may be performed by the imaging device 102. The blocks of the method 500 may be executed based on instructions stored in a non-transitory computer-readable medium, as will be readily understood. The non-transitory computer-readabie medium may indude, for example, digital memories, magnetic storage media, such as magnetic disks and magnetic tapes, hard drives, or optically readaMe digital data storage media.

[0070] The method starts at biddk 502 and proceeds to Mode 504: At block 504, a scan request is received by imaging device 102. The scan request is received by the imaging device 102 from a server, such as the server 106 which in turn may have received the scan request from a user device, such as user device 104-1. In an example, the scan request may be an «nail. The «nail may comprise a read receipt which may indicate to the imaging device 102 that the «mail is a scan request. As explained earlier, the scan request comprises a contact identifier, such as «nail address, mobile number, fax number of toe user.

[0071] At block 506, the imaging device 102 determines if toe contact identifier is authorized for s«iding the scan request. In an example, an authentication engine, such as the authentication engine 314, may determine if the contact identifier is authorized to send a scan request to toe imaging device 102. The imaging device 102 may access a list of authorized contact identifiers and based on a comparison between the received contact identifier and the list of authorized contact id«itifiers, toe imaging device 102 may determine if toe received contact identifier is authorized or not. If it is determined that toe received contact identifier is not authorized, toe scan request is discarded, and the method stops at block 524. if it is determined that the received contact identifier if authorized, the method proceeds to block 508.

[0072] At block 508, imaging device creates a proxy scan job corresponding to the scan request received at block 504. The method further proceeds to block 510, where a password corresponding to the created proxy scan job is generated and transmitted to the server. The server further transmits the password to the user. In an example implementation, as explained previously, while the proxy scan job corresponding to the scan request received at block 504 may be created at the time of receipt of the scan request, toe generation of the password corresponding to the scan job may be reserved for a later instance of time.

[0073] At block 512 toe imaging device 102 receives a selection of toe proxy scan job. A user may select the proxy scan job through an user interface of the imaging device 102 to indicate to the imaging device 102 that toe proxy scan job is to executed. At block 514, the imaging device 102 receives toe password as a user input which may be entered into toe imaging device 102 via the user interface. In an example, in response to the receiving selection of toe scan job identifier, the imaging device 102 may provide a prompt for toe user to provide toe password. The user may thereafter provide toe password to toe imaging device 102.

[0074] At block 516, upon receiving the password, toe imaging device 102 executes the proxy scan job to scan a document. In an example, the proxy scan job is executed after successful authentication of the password provided by the user. If the user inputs an incorrect password, i.e., a password other than the password which is transmitted to the contact identifier, the authentication is unsuccessful, and the proxy scan job is not executed.

[0075] At block 518, toe scanned document is transmitted to toe contact identifier of the user. For example, if the contact identifier is an email address, the scanned document is sent as an email to toe email address. Further, in a case the contact identifier is a mobile number, the scanned document may be sent to toe mobile number, may be as a multimedia message. [0076] Thereafter, the method proceeds to the decision block 520 where it is determined if the scanned data is to be printed, in an example, the user may provide an instruction to print die scanned data. If the determination made at block 520 is negative, the method proceeds to block 524 and stops.

[0077] However, if it is determined that scanned document is to be printed, the method proceeds to block 522 and ah indication of toe contact identifier is included in toe printed document. Thereafter, method proceeds to block 524 and terminates.

[0078] Figure 6 illustrates a computing environment implementing a non- transitory computer-readable medium for securing access to a document scanned by an imaging device, according to an example. In an example, toe computing environment 600 may comprise an imaging device, such as imaging device 102. The computing environment 600 includes a processing resource 604 communicatively coupled to the non-transitory computer-readable medium 602 through a communication link 606. In an example, the processing resource 604 may be a processor of toe imaging device that fetches and executes computer-readable instructions from the non-transitory computer-readable medium 602.

[0079] The non-transitory computer-readable medium 602 can be, for example, an internal memory device or an external memory device. In an example, toe communication link 606 may be a direct communication link, such as any memory read/write interface. In another example, the communication link 606 may be an indirect communication link, such as a network interface. In such a case, the processing resource 604 can access the non-transitory computer- readable medium 602 through a network 608. The network 608 may be a single network or a combination of multiple networks and may use a variety of different communication protocols.

[0080] The processing resource 604 and toe non-transitory computer- readable medium 602 may also be communicatively coupled to data sources 610. The data source(s) 610 may be used to store details, such as contact identifier, proxy scan job, scan job identifier, password in an example. In an example, the non-transitory computer-readable medium 602 comprises executable instructions 612 scanning and transmitting the scanned document. For example, the non-transitory computer-readable medium 602 may comprise instructions executable to implement the previously described communication engine 202 and scan engine 112.

[00813 In an example, the instructions 612 may cause the processing resource 604 to receive, at an Imaging device, a scan request from a contact identifier. As apparent from the previous description, the scan request is a command for executing a scanning operation at the imaging device in an example, the scan request may be received from the contact identifier of a user. In an example, the contact identifier may be an «nail address, a mobile number, a fax number. Further, the instructions 612 may cause the processing resource 604 to create a proxy scan job. The proxy scan job may be understood as toe executable commands which can be executed to perform a scanning operation.

[0082] The instructions 612 may further cause the processing resource

604 to generate a password for the proxy scan job and associate the password with toe corresponding proxy scan job. The instruction 612 further causes toe password to be transmitted to toe contact identifier.

[0083] Further, the instruction 612 may cause toe processing resource 604 to allow selection toe proxy scan job. In response to toe selection, toe instruction 612 may, thereafter, cause the processing resource 604 to provide a prompt to toe user to provide toe password. After toe password is provided to the imaging device, the instruction 612 may cause toe processing resource 604 to compare the received password with the password associated with the proxy scan job. If toe received password is same as of the password associated with the proxy scan job, toe instructions 612 may cause toe processing resource 604 to execute toe proxy scan job to scan a document. The instruction 612 may further cause the processing resource 604 to transmit toe scanned to toe contact identifier.

[0084] In an example, the instruction 612 may cause the processing resource 604 to print the scanned document. In an example, a user may provide an instruction to print the scanned document and in response to the receiving the instruction, the instruction 612 causes the processing resource to print the scanned document While printing the scanned document, the instruction 612 may cause the processing resource 604 to include an indication of toe contact identifier in the printed document. For example, if the contact identifier is an email, say ryan@domainname.com, toe instruction 612 may cause toe processing resource 604 to include an indication in toe printed document that the printing operation is performed in tandem with a scan operation performed further to a scan request initiated by ryan@domainname.com.

[0085] Thus, toe methods and devices of toe present subject matter provides techniques for securely scanning of toe document. Although implementations of scanning of document have been described in a language specific to structural features and/or methods, it is to be understood that toe appended claims are not necessarily limited to toe specific features or methods described. Rather, toe specific features and methods are disclosed as example for remote scanning of a document