IP Library Granted Patent US 12,225,039
Granted Patent B2
US 12,225,039 · App. 17/555,125 · Granted Feb 11, 2025

Policy driven vulnerability identification and remediation

Inventor: Brandon Edward Rose (Phoeniz, AZ)
Assignee: Netskope, Inc.
H04L63/1433G06N5/04G06N20/00H04L45/42H04L45/74H04L63/0236H04L63/20H04L67/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,225,039
App. No.
17/555,125
Granted
Feb 11, 2025
Kind
B2
Abstract

A system for policy based vulnerability management of a network equipment of an enterprise is disclosed. A plurality of vulnerabilities associated with an end user device and a plurality of policies associated with the plurality of vulnerabilities is identified. Security risks associated with the plurality of vulnerabilities based on a type of the plurality of vulnerabilities are identified. Remediation for the plurality of vulnerabilities is determined based on the plurality of policies and prioritized based on the vulnerabilities, the security risks, and the policies. The plurality of policies is based on a cloud service selected from the end user device, a tenant, and a role associated with the end user device. A route corresponding to the plurality of policies and the cloud service is identified. The route specifies the end user device or a mid-link server. The cloud service is provided to the end user device via the route.

Claims (75)

1. A cloud-based multi-tenant system for policy based vulnerability management of a network equipment of an enterprise, the cloud-based multi-tenant system comprising:

an application running on an end user device of a plurality of end user devices that selects a cloud service from a plurality of cloud services;

a plurality of routes through the cloud-based multi-tenant system to deliver the plurality of cloud services to the plurality of end user devices, wherein:

the plurality of routes is specified for a plurality of policies; and

a mid-link server configured to:

identify a plurality of vulnerabilities associated with a plurality of firmware of the end user device;

identify security risks associated with the plurality of vulnerabilities based on a type of the plurality of vulnerabilities;

identify the plurality of policies associated with the plurality of vulnerabilities based on the type of the plurality of vulnerabilities and the end user device, wherein the plurality of policies is specified for the plurality of end user devices;

determine remediation for the plurality of vulnerabilities based on the plurality of policies, wherein:

the plurality of policies is set based on the cloud service, a tenant of the end user device, and/or a user role associated with the end user device;

identify a route from the plurality of routes corresponding to the plurality of policies and the cloud service, wherein the route specifies the end user device or the mid-link server;

prioritize the remediation of the plurality of firmware based on the type of the plurality of vulnerabilities, the security risks, and the plurality of policies;

execute the remediation of the plurality of firmware by upgrading the plurality of firmware based on the plurality of policies according to the prioritization; and

establish communication via the route between the application and the cloud service based on the plurality of policies.

2. The cloud-based multi-tenant system for the policy based vulnerability management of the network equipment of the enterprise as recited in claim 1 , wherein:

the plurality of vulnerabilities is identified based on a first machine learning algorithm; and

the remediation of the plurality of vulnerabilities is prioritized using a second machine learning algorithm.

3. The cloud-based multi-tenant system for the policy based vulnerability management of the network equipment of the enterprise as recited in claim 1 , wherein the plurality of vulnerabilities associated with the end user device include vulnerabilities associated with at least one of firmware, application software, system software, programs, operating systems, freeware, groupware, shareware, bundled software, or spreadsheets.

4. The cloud-based multi-tenant system for the policy based vulnerability management of the network equipment of the enterprise as recited in claim 1 , wherein the remediation is performed by an administrator through the mid-link server.

5. The cloud-based multi-tenant system for the policy based vulnerability management of the network equipment of the enterprise as recited in claim 1 , wherein the mid-link server is further configured to:

extract:

configuration items using Application Programming Interfaces (APIs) from a configuration database, wherein the configuration items include hostnames, IP addresses, models, make, roles, or software versions of the plurality of firmware, wherein the plurality of firmware is associated with the plurality of end user devices,

device configurations from a device configuration repository, wherein the device configurations include vendor specific information, and

external vulnerability information from a plurality of data sources including external websites, social media, and/or vendor websites;

correlate the configuration items, the device configurations, and the external vulnerability information; and

identify at least one vulnerability associated with the plurality of firmware based on the correlation.

6. The cloud-based multi-tenant system for the policy based vulnerability management of the network equipment of the enterprise as recited in claim 1 , wherein firmware of the plurality of end user devices that are lacking firewalls are assigned a higher priority for the remediation and firmware that is within a private network or the firmware that do not have public Internet Protocol (IP) addresses are assigned a lower priority of the remediation.

7. The cloud-based multi-tenant system for the policy based vulnerability management of the network equipment of the enterprise as recited in claim 1 , wherein the plurality of policies varies with each tenant of a plurality of tenants of the cloud-based multi-tenant system.

8. The cloud-based multi-tenant system for the policy based vulnerability management of the network equipment of the enterprise as recited in claim 1 , wherein at least one policy from the plurality of policies disables access to the cloud service based on a type of vulnerabilities associated with the end user device.

9. A vulnerability identification and remediation method for a network equipment in a cloud-based multi-tenant system of an enterprise, the method comprising:

receiving from an application running on an end user device of a plurality of end user devices, a selection of a cloud service from a plurality of cloud services;

identifying at a mid-link server, a plurality of vulnerabilities associated with a plurality of firmware of the end user device;

identifying security risks associated with the plurality of vulnerabilities based on a type of the plurality of vulnerabilities;

identifying at the mid-link server, a plurality of policies associated with the plurality of vulnerabilities based on the type of the plurality of vulnerabilities and the end user device, wherein the plurality of policies is specified for the plurality of end user devices;

determining at the mid-link server, remediation for the plurality of vulnerabilities based on the plurality of policies, wherein the plurality of policies is based on the cloud service, a tenant of the end user device, and/or a user role associated with the end user device;

identifying at the mid-link server, a route from a plurality of routes corresponding to the plurality of policies and the cloud service, wherein:

the route specifies the end user device or the mid-link server;

the plurality of routes is specified for the plurality of policies; and

the plurality of routes through the cloud-based multi-tenant system delivers the plurality of cloud services to the plurality of end user devices;

prioritizing at the mid-link server, the remediation of the plurality of firmware based on the type of the plurality of vulnerabilities, the security risks, and the plurality of policies;

executing remediation of the plurality of firmware by upgrading the plurality of firmware based on the plurality of policies according to the priority; and

establishing by the mid-link server, communication via the route between the application and the cloud service based on the plurality of policies.

10. The vulnerability identification and remediation method for the network equipment in the cloud-based multi-tenant system of the enterprise as recited in claim 9 , further comprising:

extracting:

configuration items using Application Programming Interfaces (APIs) from a configuration database, wherein the configuration items include hostnames, IP addresses, models, make, roles, or software versions of the plurality of firmware, wherein the plurality of firmware is associated with the plurality of end user devices,

device configurations from a device configuration repository, wherein the device configurations include vendor specific information, and

external vulnerability information from a plurality of data sources including external websites, social media, and/or vendor websites;

correlating the configuration items, the device configurations, and the external vulnerability information; and

identifying at least one vulnerability associated with the plurality of firmware based on the correlation.

11. The vulnerability identification and remediation method for the network equipment in the cloud-based multi-tenant system of the enterprise as recited in claim 9 , wherein firmware lacking firewall is assigned a higher priority for the remediation.

12. The vulnerability identification and remediation method for the network equipment in the cloud-based multi-tenant system of the enterprise as recited in claim 9 , wherein the plurality of vulnerabilities associated with the end user device include vulnerabilities associated with at least one of firmware, application software, system software, programs, operating systems, freeware, groupware, shareware, bundled software, or spreadsheets.

13. The vulnerability identification and remediation method for the network equipment in the cloud-based multi-tenant system of the enterprise as recited in claim 9 , wherein firmware that is within a private network or the firmware that do not have public Internet Protocol (IP) addresses are assigned a lower priority of remediation.

14. The vulnerability identification and remediation method for the network equipment in the cloud-based multi-tenant system of the enterprise as recited in claim 9 , wherein the plurality of policies varies with each tenant of a plurality of tenants of the cloud-based multi-tenant system.

15. The vulnerability identification and remediation method for the network equipment in the cloud-based multi-tenant system of the enterprise as recited in claim 9 , wherein the remediation is performed by an administrator through the mid-link server.

16. A cloud-based multi-tenant system for policy-based vulnerability management, the cloud-based multi-tenant system comprising one or more processors and one or more memories with code for:

extracting:

configuration items associated with a plurality of firmware of a plurality of end user devices from a configuration database using Application Programming Interfaces (APIs),

device configurations including vendor specific information from a device configuration repository, and

external vulnerability information including external websites, social media, and/or vendor web sites from a plurality of data sources;

correlating the configuration items, the device configurations, and the external vulnerability information; and

identifying a plurality of vulnerabilities associated with the plurality of firmware based on the correlation;

receiving from an application running on an end user device of the plurality of end user devices, a selection of a cloud service from a plurality of cloud services;

identifying security risks associated with the plurality of vulnerabilities based on a type of the plurality of vulnerabilities;

identifying a plurality of policies associated with the plurality of vulnerabilities based on the type of the plurality of vulnerabilities and the end user device, wherein the plurality of policies is specified for the plurality of end user devices;

determining remediation for the plurality of vulnerabilities based on the plurality of policies, wherein the plurality of policies is based on the cloud service, a tenant of the end user device, and/or a user role associated with the end user device;

identifying a route from a plurality of routes corresponding to the plurality of policies and the cloud service, wherein:

the route specifies the end user device or a mid-link server of the cloud-based multi-tenant system;

the plurality of routes is specified for the plurality of policies; and

the plurality of routes through the cloud-based multi-tenant system delivers the plurality of cloud services to the plurality of end user devices;

executing the remediation of the plurality of firmware by upgrading the plurality of firmware based on the plurality of policies; and

communicating via the route between the application and the cloud service based on the plurality of policies.

17. The cloud-based multi-tenant system for the policy-based vulnerability management as recited in claim 16 , further comprising prioritizing the remediation of the plurality of firmware based on the type of the plurality of vulnerabilities, the security risks, and the plurality of policies.

18. The cloud-based multi-tenant system for the policy-based vulnerability management as recited in claim 16 , wherein the plurality of policies varies with each tenant of a plurality of tenants of the cloud-based multi-tenant system.

19. The cloud-based multi-tenant system for the policy-based vulnerability management as recited in claim 16 , wherein the remediation is performed by an administrator through the mid-link server.

20. The cloud-based multi-tenant system for the policy-based vulnerability management as recited in claim 16 , wherein the configuration items include hostnames, IP addresses, models, make, roles, or software versions of the plurality of firmware.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 20, 2021
From: ROSE, BRANDON EDWARD
To: NETSKOPE, INC.
Reel/Frame 058436/0323 →
Continuity (3)
Continuation 17339525 · Jun 4, 2021
Continuation 17315010 · May 7, 2021
Related Publication 20220360602A1 · Nov 10, 2022
References Cited (137)
US 5440723A · Arnold et al. · 1995 [cited by applicant]
US 6513122B1 · Magdych et al. · 2003 [cited by applicant]
US 6622248B1 · Hirai · 2003 [cited by applicant]
US 7080408B1 · Pak et al. · 2006 [cited by applicant]
US 7298864B2 · Jones · 2007 [cited by applicant]
US 7376719B1 · Shafer et al. · 2008 [cited by applicant]
US 7627891B2 · Williams · 2009 [cited by applicant]
US 7735116B1 · Gauvin · 2010 [cited by applicant]
US 7966654B2 · Crawford · 2011 [cited by applicant]
US 7975286B1 · Fickey · 2011 [cited by applicant]
US 8000329B2 · Fendick et al. · 2011 [cited by applicant]
US 8065712B1 · Cheng · 2011 [cited by applicant]
US 8256002B2 · Chandrashekhar · 2012 [cited by applicant]
US 8296178B2 · Hudis et al. · 2012 [cited by applicant]
US 8499330B1 · Albisu · 2013 [cited by applicant]
US 8595844B2 · Bahl · 2013 [cited by applicant]
US 8793151B2 · DelZoppo et al. · 2014 [cited by applicant]
US 8839417B1 · Jordan · 2014 [cited by applicant]
US 9197601B2 · Pasdar · 2015 [cited by applicant]
US 9225734B1 · Hastings · 2015 [cited by applicant]
US 9231968B2 · Fang et al. · 2016 [cited by applicant]
US 9280678B2 · Redberg · 2016 [cited by applicant]
US 9467465B2 · Hibbert · 2016 [cited by applicant]
US 9811662B2 · Sharpe et al. · 2017 [cited by applicant]
US 10027538B1 · Okita · 2018 [cited by examiner]
US 10033766B2 · Gubta · 2018 [cited by applicant]
US 10084825B1 · Xu · 2018 [cited by applicant]
US 10142362B2 · Weith · 2018 [cited by applicant]
US 10237282B2 · Nelson et al. · 2019 [cited by applicant]
US 10334442B2 · Vaughn et al. · 2019 [cited by applicant]
US 10382468B2 · Dods · 2019 [cited by applicant]
US 10484334B1 · Lee et al. · 2019 [cited by applicant]
US 10554418B2 · Kshirsagar · 2020 [cited by examiner]
US 10691796B1 · Stolte · 2020 [cited by applicant]
US 10826941B2 · Jain et al. · 2020 [cited by applicant]
US 11032301B2 · Mandrychenko et al. · 2021 [cited by applicant]
US 11036856B2 · Graun et al. · 2021 [cited by applicant]
US 11201891B2 · Davis · 2021 [cited by applicant]
US 11233815B1 · Rose · 2022 [cited by applicant]
US 11281775B2 · Burdett et al. · 2022 [cited by applicant]
US 20020099666A1 · Dryer et al. · 2002 [cited by applicant]
US 20030055994A1 · Herrmann et al. · 2003 [cited by applicant]
US 20030063321A1 · Inoue et al. · 2003 [cited by applicant]
US 20030172292A1 · Judge · 2003 [cited by applicant]
US 20030204632A1 · Willebeek-Lemair et al. · 2003 [cited by applicant]
US 20040015719A1 · Lee et al. · 2004 [cited by applicant]
US 20050010593A1 · Fellenstein et al. · 2005 [cited by applicant]
US 20050271246A1 · Sharma et al. · 2005 [cited by applicant]
US 20060156401A1 · Newstadt et al. · 2006 [cited by applicant]
US 20060195905A1 · Fudge · 2006 [cited by applicant]
US 20070204018A1 · Chandra et al. · 2007 [cited by applicant]
US 20070237147A1 · Quinn et al. · 2007 [cited by applicant]
US 20080069480A1 · Aarabi et al. · 2008 [cited by applicant]
US 20080134332A1 · Keohane et al. · 2008 [cited by applicant]
US 20090144818A1 · Kumar et al. · 2009 [cited by applicant]
US 20090249470A1 · Litvin et al. · 2009 [cited by applicant]
US 20090300351A1 · Lei et al. · 2009 [cited by applicant]
US 20100017436A1 · Wolge · 2010 [cited by applicant]
US 20110119481A1 · Auradkar et al. · 2011 [cited by applicant]
US 20110145594A1 · Jho et al. · 2011 [cited by applicant]
US 20120278896A1 · Fang et al. · 2012 [cited by applicant]
US 20130086376A1 · Haynes · 2013 [cited by applicant]
US 20130159694A1 · Chiueh et al. · 2013 [cited by applicant]
US 20130298190A1 · Sikka et al. · 2013 [cited by applicant]
US 20130347085A1 · Hawthorn et al. · 2013 [cited by applicant]
US 20140013112A1 · Cidon et al. · 2014 [cited by applicant]
US 20140068030A1 · Chambers et al. · 2014 [cited by applicant]
US 20140068705A1 · Chambers et al. · 2014 [cited by applicant]
US 20140259093A1 · Narayanaswamy et al. · 2014 [cited by applicant]
US 20140259095A1 · Bryant · 2014 [cited by applicant]
US 20140282843A1 · Buruganahalli et al. · 2014 [cited by applicant]
US 20140359282A1 · Shikfa et al. · 2014 [cited by applicant]
US 20140366079A1 · Pasdar · 2014 [cited by applicant]
US 20150100357A1 · Seese et al. · 2015 [cited by applicant]
US 20160323318A1 · Terrill et al. · 2016 [cited by applicant]
US 20160350145A1 · Botzer et al. · 2016 [cited by applicant]
US 20170064005A1 · Lee · 2017 [cited by applicant]
US 20170093917A1 · Chandra et al. · 2017 [cited by applicant]
US 20170250869A1 · Voellmy · 2017 [cited by applicant]
US 20170250951A1 · Wang et al. · 2017 [cited by applicant]
US 20170359271A1 · Koh · 2017 [cited by examiner]
US 20170373860A1 · Kshirsagar · 2017 [cited by examiner]
US 20180137288A1 · Polyakov · 2018 [cited by applicant]
US 20180139221A1 · Chen · 2018 [cited by applicant]
US 20200050686A1 · Kamalapuram et al. · 2020 [cited by applicant]
US 20200242269A1 · Narayanaswamy · 2020 [cited by applicant]
US 20210173710A1 · Crossley · 2021 [cited by applicant]
US 20210185015A1 · Sapp · 2021 [cited by applicant]
US 20210234892A1 · Narayanaswamy · 2021 [cited by applicant]
CN 109690492 · 2019 [cited by applicant]
EP 1063833A2 · 2000 [cited by applicant]
EP 3654220 · 2020 [cited by applicant]
EP 2959422 · 2021 [cited by applicant]
KR 101113615 · 2012 [cited by applicant]
WO 2021138299 · 2021 [cited by applicant]
Martin, Victoria “Cooperative Security Fabric,” The Fortinet Cookbook, Jun. 8, 2016, 6 pgs., archived Jul. 28, 2016 at https://web.archive.org/web/20160728170025/http://cookbook.fortinet.com/cooperative-security-fabric-… [cited by applicant]
Huckaby, Jeff Ending Clear Text Protocols, Rackaid.com, Dec. 9, 2008, 3 pgs. [cited by applicant]
Nevvton, Harry “fabric,” Newton's Telecom Dictionary, 30th Updated, Expanded, Anniversary Edition, 2016, 3 pgs. [cited by applicant]
Fortinet, “Fortinet Security Fabric Earns 100% Detection Scores Across Several Attack Vectors in NSS Labs′ Latest Breach Detection Group Test [press release]”, Aug. 2, 2016, 4 pgs, available at https://www.fortinet.com/… [cited by applicant]
Fortinet, “Fortinet Security Fabric Named 2016 CRN Network Security Product of the Year [press release]”, Dec. 5, 2016, 4 pgs, available at https://www.fortinet.com/corporate/about-us/newsroom/press-releases/2016/fortin… [cited by applicant]
McCullagh, Declan, “How safe is instant messaging? A security and privacy survey,” CNET, Jun. 9, 2008, 14 pgs. [cited by applicant]
Beck et al. “IBM and Cisco: Together for a World Class Data Center,” IBM Redbooks, Jul. 2013, 654 pgs. [cited by applicant]
Martin, Victoria “Installing internal FortiGates and enabling a security fabric,” The Fortinet Cookbook, Jun. 8, 2016, 11 pgs, archived Aug. 28, 2016 at https://web.archive.org/web/20160828235831/http://cookbook.fortine… [cited by applicant]
Zetter, Kim, “Revealed: The Internet's Biggest Security Hole,” Wired, Aug. 26, 2008, 13 pgs. [cited by applicant]
Adya et al., Farsite: Federated, available, and reliable storage for an incompletely trusted environment, SIGOPS Oper. Syst. Rev. 36, SI, Dec. 2002, pp. 1-14. [cited by applicant]
Agrawal et al., “Order preserving encryption for numeric data,” In Proceedings of the 2004 ACM SIGCOMM international conference on Management of data, Jun. 2004, pp. 563-574. [cited by applicant]
Balakrishnan et al., “A layered naming architecture for the Internet,” ACM SIGCOMM Computer Communication Review, 34(4), 2004, pp. 343-352. [cited by applicant]
Downing et al. , Naming Dictionary of Computer and Internet Terms, (11th Ed.) Barron's, 2013, 6 pgs. [cited by applicant]
Downing et al., Dictionary of Computer and Internet Terms, (10th Ed.) Barron's, 2009, 4 pgs. [cited by applicant]
Zoho Mail, “Email Protocols: What they are & their different types,” 2006, 7 pgs. available at https://www.zoho.com/mail/glossary/email-protocols.html#:˜: text=mode of communication.-,What are the different email protoc… [cited by applicant]
NIIT, Special Edition Using Storage Area Networks, Que, 2002, 6 pgs. [cited by applicant]
Chapple, Mike, “Firewall redundancy: Deployment scenarios and benefits,” Tech Target, 2005, 5 pgs. available at https://www.techtarget.com/searchsecurity/tip/Firewall-redundancy-Deployment-scenarios-and-benefits?%20Offe… [cited by applicant]
Fortinet, FortiGate—3600 User Manual (vol. 1 , Version 2.50 MR2) Sep. 5, 2003, 329 pgs. [cited by applicant]
Fortinet, FortiGate SOHO and SMB Configuration Example, (Version 3.0 MR5), Aug. 24, 2007, 54 pgs. [cited by applicant]
Fortinet, FortiSandbox—Administration Guide, (Version 2.3.2), Nov. 9, 2016, 191 pgs. [cited by applicant]
Fortinet, FortiSandbox Administration Guide, (Version 4.2.4) Jun. 12, 2023, 245 pgs. available at https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/fba32b46-b7c0-11ed-8e6d-fa163e15d75b/FortiSandbox-4… [cited by applicant]
Fortinet,FortiOS—Administration Guide, (Versions 6.4.0), Jun. 3, 2021, 1638 pgs. [cited by applicant]
Heady et al., “The Architecture of a Network Level Intrusion Detection System,” University of New Mexico, Aug. 15, 1990, 21 pgs. [cited by applicant]
Kephart et al., “Fighting Computer Viruses,” Scientific American (vol. 277, No. 5) Nov. 1997, pp. 88-93. [cited by applicant]
Wang, L., Chapter 5: Cooperative Security in D2D Communications, “Physical Layer Security in Wireless Cooperative Networks,” 41 pgs. first online on Sep. 1, 2017 at https://link.springer.com/chapter/%2010.1007/978-3-319… [cited by applicant]
Lee et al., “A Data Mining Framework for Building Intrusion Detection Models,” Columbia University, n.d. 13 pgs. [cited by applicant]
Merriam-Webster Dictionary, 2004, 5 pgs. [cited by applicant]
Microsoft Computer Dictionary, (5th Ed.), Microsoft Press, 2002, 8 pgs. [cited by applicant]
Microsoft Computer Dictionary, (4th Ed.), Microsoft Press, 1999, 5 pgs. [cited by applicant]
Mika et al. “Metadata Statistics for a Large Web Corpus,” LDOW2012, Apr. 16, 2012, 6 pgs. [cited by applicant]
Oxford Dictionary of Computing (6th Ed.), 2008, 5 pgs. [cited by applicant]
Paxson, Vern, “Bro: a System for Detecting Network Intruders in Real-Time,” Proceedings of the 7th USENIX Security Symposium, Jan. 1998, 22 pgs. [cited by applicant]
Fortinet Inc., U.S. Appl. No. 62/503,252, “Building a Cooperative Security Fabric of Hierarchically Interconnected Network Security Devices.” n.d., 87 pgs. [cited by applicant]
Song et al., “Practical techniques for searches on encrypted data,” In Proceeding 2000 IEEE symposium on security and privacy. S&P. 2000, May 2000, pp. 44-55. [cited by applicant]
Dean, Tamara, Guide to Telecommunications Technology, Course Technology, 2003, 5 pgs,. [cited by applicant]
U.S. Appl. No. 60/520,577, “Device, System, and Method for Defending a Computer Network,” Nov. 17, 2003, 21 pgs. [cited by applicant]
U.S. Appl. No. 60/552,457, “Fortinet Security Update Technology,” Mar. 2004, 6 pgs. [cited by applicant]
Tittel, Ed, Unified Threat Management For Dummies, John Wiley & Sons, Inc., 2012, 76 pgs. [cited by applicant]
Fortinet, FortiOS Handbook: UTM Guide (Version 2), Oct. 15, 2010, 188 pgs. [cited by applicant]
Full Definition of Security, Wayback Machine Archive of Merriam-Webster on Nov. 17, 2016, 1 pg. [cited by applicant]
Definition of Cooperative, Wayback Machine Archive of Merriam-Webster on Nov. 26, 2016, 1 pg. [cited by applicant]
Pfaffenberger, Bryan, Webster's New World Computer Dictionary, (10th Ed.), 2003, 5 pgs. [cited by applicant]