The subject matter described herein relates to implementing security intelligence into a security gateway element (SGE) to provide network monitoring and remediation services at the SGE. More particularly, the subject matter described herein relates to methods, systems, and computer readable media for utilizing a security service engine to assess security vulnerabilities on a security gateway element.
A security gateway element, such as a session border controller, is a network element that is deployed in a communications network and configured to manage and regulate internet protocol communication traffic flows. The security gateway element is usually deployed at the border of the communication network, such as an enterprise network, in order to control the internet protocol (IP) communication sessions that traverse the security gateway element. A security gateway element can be configured to provide protection against denial-of-service attacks, safeguard against toll fraud and service theft, provide protection against malicious packet traffic, and encrypt signaling messages and media traffic messages. To implement these security features, the security gateway element traditionally needs to be subjected to a secure configuration, third-party software management, and real-time network traffic control. At present, a secure configuration is commonly achieved by providing a security configuration guide to a system administrator. However, such an approach in no way guarantees that the security gateway element is actually configured in a secure manner. Likewise, the general approach to third-party software management is to manually check each software component present in the security gateway element and ensure that there are no existing security vulnerabilities. However, such manual security checks are extremely time consuming and resource intensive. Moreover, while the dynamic traffic flow control of the security gateway element can be managed by parameters from a provisioned security configuration, such an approach provides an unsuitable mechanism capable to adapting to actual network traffic flow conditions in real time.
Accordingly, there exists a need for methods, systems, and computer readable media for utilizing a security service engine to assess security vulnerabilities on a security gateway element.
The subject matter described herein includes a methods, systems, and computer readable media for utilizing a security service engine (SSE) to assess security vulnerabilities on a security gateway element (SGE). One method includes establishing a security configuration for a SGE corresponding to a provisioned security service policy definition and configuring a plurality of SGE security service managers hosted by a SSE on the SGE based on policies included in the security service policy definition. The method further includes executing, by the SSE, each of the plurality of SGE security service managers as a software based service in real time to enforce the policies of the security service policy definition on the SGE and remediating the security configuration of the SGE if one or more of the plurality of SGE security service managers detects a security vulnerability corresponding to the operation of the SGE.
In one example of the method, the SGE includes a session border controller (SBC), a firewall, a Web service gateway, or a virtual private network (VPN) server.
In one example of the method, one of the plurality of SGE security service managers includes a SGE component security manager that is configured facilitate a security service that assesses security vulnerabilities of the SGE based on hardware component information and software component information obtained from the SGE.
In one example of the method, one of the plurality of SGE security service managers includes a network security status manager that is configured to facilitate a security service that assesses security vulnerabilities of management ports and service ports of the SGE.
In one example of the method, one of the plurality of SGE security service managers includes a SGE security configuration manager that is configured to facilitate a security service that assesses security vulnerabilities of the SGE based on a current security configuration of the SGE.
In one example of the method, one of the plurality of SGE security service managers includes a network traffic security analysis manager that is configured to facilitate a security service that assesses security vulnerabilities of the SGE based on an analysis of incoming and outgoing network traffic traversing via the SGE.
In one example of the method, one of the plurality of SGE security service managers includes an analytics security service manager that is configured to facilitate a security service that assesses security vulnerabilities of the SGE through systematic analysis of data and statistics collected from the SGE under operation.
A system for utilizing a security service engine to assess security vulnerabilities on a security gateway element includes a session gateway element comprising at least one processor and memory. The system further includes a security service engine stored in the memory and when executed by the at least one processor is configured to establish a security configuration for the SGE corresponding to a provisioned security service policy definition, to configure a plurality of SGE security service managers hosted by the SSE based on policies included in the security service policy definition, to execute each of the plurality of SGE security service managers as a software based service in real time to enforce the policies of the security service policy definition on the SGE, and to remediate the security configuration of the SGE if one or more of the plurality of SGE security service managers detects a security vulnerability corresponding to the operation of the SGE.
In one example of the system, the SGE includes a session border controller, a firewall, a Web service gateway, or a virtual private network server.
In one example of the system, one of the plurality of SGE security service managers includes a SGE component security manager that is configured facilitate a security service that assesses security vulnerabilities of the SGE based on hardware component information and software component information obtained from the SGE.
In one example of the system, one of the plurality of SGE security service managers includes a network security status manager that is configured to facilitate a security service that assesses security vulnerabilities of management ports and service ports of the SGE.
In one example of the system, one of the plurality of SGE security service managers includes a SGE security configuration manager that is configured to facilitate a security service that assesses security vulnerabilities of the SGE based on a current security configuration of the SGE.
In one example of the system, one of the plurality of SGE security service managers includes a network traffic security analysis manager that is configured to facilitate a security service that assesses security vulnerabilities of the SGE based on an analysis of incoming and outgoing network traffic traversing via the SGE.
In one example of the system, one of the plurality of SGE security service managers includes an analytics security service manager that is configured to facilitate a security service that assesses security vulnerabilities of the SGE through systematic analysis of data and statistics collected from the SGE under operation.
The subject matter described herein may be implemented in hardware, software, firmware, or any combination thereof. As such, the terms “function” “node” or “engine” as used herein refer to hardware, which may also include software and/or firmware components, for implementing the feature being described. In one exemplary implementation, the subject matter described herein may be implemented using a non-transitory computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer control the computer to perform steps. Exemplary computer readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.
Methods, systems, and computer readable media for utilizing a security service engine (SSE) to assess security vulnerabilities on a security gateway element (SGE) are disclosed. In some embodiments, the disclosed subject matter includes a security gateway element, such as session border controller, that is provisioned with a security intelligence engine that provides a security service that is configured to evaluate a security configuration of the security gateway element as well as assigning a security score corresponding to the security configuration. The security intelligence engine can also be configured to issue a report or alert in the event a weak security configuration is detected. The security intelligence engine is further configured to collect version information corresponding to any third-party software that is provisioned on the security gateway element. After obtaining diversion data, the security gateway element can verify if there are any security vulnerabilities associated with currently provisioned software application(s).
In some embodiments, a third-party software database can be built and maintained on a third-party services server. Notably, the security service engine can be configured to check if there is any new security concern or issue regarding its provision software applications. For example, the security service engine can be configured to periodically send a query message that contains version information of its provision software applications to the oracle server. In some embodiments, the query message can be sent in response to a new software application that is provisioned on the security gateway element.
The security service engine can also be configured to conduct dynamic traffic flow control by inspecting network traffic packets that are received either from a trusted domain or an untrusted domain. In particular, the security service engine is able to determine whether the network traffic that is traversing the security gateway element is suspicious or malicious. Depending on the security policy corresponding to the provision security configuration, the security service engine is able to conduct dynamic control changes that enable the blocking of any malicious network traffic. The security service engine is also able to report the presence of any detected suspicious traffic and to make security configuration recommendations that can improve network traffic control at the security gateway element. In addition, the security service engine can be configured to directly communicate with any new fraud and threat detection technologies in order to improve its traffic control capabilities.
As shown in
As shown in
In some embodiments, SSE 206 includes a security service policy manager 208 that is configured to receive service security policy definitions as input. In some embodiments, security service policy manager 208 is configured to distribute and apply the security service policy definition to a plurality of SGE security service managers 210-218 (as described below). Security service engine 206 further includes a security report and remediation manager 220 that is configured to issue an alert and/or report when SSE 206 and/or a SGE security service manager detects a security vulnerability present in SGE 106.
As disclosed herein, a security service policy definition that is received for provisioning (e.g., from a security configuration manager) can be used to define the appropriate behavior of the security services provisioned on SGE 106. For example, a security service policy definition can establish the manner in which security issues are reported and the manner in which security issues are remediated by the security report and remediation manager 220 included in SSE 206. Further, the security service policy definition can define one or more remediation actions that can be executed by manager 220 based on a security assessment conducted by the security service engine. For instance, if SSE 206 determines after using a SGE component security check manager 210 that a version of a software service application has been identified as out-of-date or presents a possible security vulnerability to SGE 106, the security service policy definition can include a software update policy that indicates that an automatic software upgrade procedure should be conducted by security report and remediation manager 220 with the security service engine.
Similarly, a security service policy definition can include network port security policies that provide a generic definition for the ports in the security gateway element as well as specific port policy definitions. In some embodiments, specific port security service policy definitions override any generic security service policy definition. Notably, these port definitions define reporting actions and remediation actions if a security assessment executed by an SGE security service manager detects a system vulnerability. For example, SSE 206 and/or security report and remediation manager 220 can report the detected security vulnerability and issue an alert to a system administrator. Such an alert can specify whether the system vulnerability is a high-risk, a medium risk, or a low risk, based upon predefined thresholds established by the particular SGE security service managers in the security service engine. The SSE 206 and/or security report and remediation manager 220 can also be configured to initiate a remediation action upon detecting the security vulnerability that includes, but is not limited to, demoting the trust level corresponding to a particular port, ceasing services associated with a detected port, and/or closing the flagged port. In some embodiments, each of the SGE security service managers includes its own separate security report and remediation manager component instead of relying on security report and remediation manager 220.
Further, the security service policy definition can include configuration security policies that can be utilized by SGE security configuration manager 214. For example, if the security service engine and/or SGE security configuration manager 214 detects a weak security configuration corresponding to SGE 106, SGE security configuration manager 214 can report that detected vulnerable configuration and issue a report or an alert to a system administrator (or instruct security report and remediation manager 220 to do so). The issued report or alert can specify whether the configuration vulnerability is a high risk, a medium risk, or a low risk. The security service engine and/or SGE security configuration manager 214 can also be configured to initiate a remediation action upon detecting the suspect configuration that includes rejecting the insecure configuration and/or reverting to a previous system configuration that was recognized as being secure.
The security service policy definition can also include real-time traffic security policies that can be utilized by a network traffic security analysis manager 216. For example, if the security service engine and/or network traffic security analysis manager 216 detects and determines that real-time network traffic traversing SGE 106 proposes a security risk, then network traffic security analysis manager 216 can issue an alert to a system administrator (or instruct manager 220 to do so). Such an alert can specify whether the real-time traffic security risk is a high-risk, a medium risk, or a low risk. Based on the degree of the detected risk, the security service engine can be configured to initiate an appropriate remediation action using manager 220. Such remediation actions can include, but are not limited to, the rejection of the network traffic at the security gateway element, demoting the trust level, ceasing service associated with the detected real-time traffic security risk, and/or closing the port servicing the detected real-time traffic.
In the description below, the functionality and operation of embodiments for each of the SGE security service managers 210-218 are described in additional detail.
In some embodiments, security service engine 306 (and/or SGE component security manager 320) is configured to assess the security vulnerabilities corresponding to the hardware components and software components residing in SGE 106. Notably, security service engine 306 (and/or SGE component security manager 320) is configured to query system services manager 310 to obtain hardware component information and software component information corresponding to hardware components 312-314 and software components 316-318, respectively. For example, security service engine 306 (and/or SGE component security manager 320) may send a query message to system services manager 310 requesting pertinent hardware information (e.g., model identification numbers and/or version numbers) and software information (e.g., software, firmware, and/or driver version numbers). After obtaining this information from system services manager 310, security service engine 306 (and/or SGE component security manager 320) establishes a connection with central security server 308. In some embodiments, central security server 308 can include a session border controller security server that is configured to maintain and store one or more databases containing hardware and software identification information that is mapped to known security issues and/or common vulnerabilities and exposures (CVE) data. In the event that the hardware information and software information provided to central security server 308 matches the database entries and corresponding security vulnerability information maintained in its local database, central security server 308 is configured to issue a report specifying the security vulnerability issues pertaining to the assessed hardware and or software information to security service engine 306. In response, security service engine 306 and/or SGE component security manager 320 may then alert a system administrator of the detected system vulnerabilities associated with the hardware and/or software components. Based on the security service policy definition, security service engine 306 (and/or SGE component security manager 320) can either utilize a report and remediation manager to issue a pop-up alert or automatically download an upgrade software patch from central security server 308 (or from a third party source/server) depending on the security service policy definition included in the security configuration provisioned on SGE 106.
In some embodiments, central security server 308 includes a security vulnerabilities database (SVDB) 322 that contains various security gateway element related information. For example, security vulnerabilities database 322 can include all of the supported release version information corresponding to the hardware and software components residing on SGE 106 in the network. For each version of hardware or software component, security vulnerabilities database 322 includes all of the third-party software component name information and version information. Further, for each version of software or hardware component, security vulnerabilities database 322 contains security policy information, such as recommended security cipher configuration data. In addition, security vulnerabilities database 322 includes a package that contains known security vulnerability information that is mapped to each hardware and software version. Further, for each third-party component, security vulnerabilities database 322 contains all known third party CVE information.
Returning to
Security service engine 206 may then determine if the service or application communicated on the selected port is secure. For example, security service engine 206 and/or network security status manager 212 can check if the service on the selected port is correct and determine whether the service is running securely on the selected port (block 408). For example, security service engine 206 and/or network security status manager 212 can detect a cipher that is not recommended for communication on port ‘443’, which is an HTTPS/TLS port on the security gateway element. The security service engine 206 and/or network security status manager 212 proceeds to apply a security policy in block 410. In some embodiments, security service engine 206 and/or network security status manager 212 executes a remedial action (e.g., using manager 220) that is as defined by the security service policy definition configured SGE 106. In some embodiments, security service engine 206 and/or network security status manager 212 may also be configured to use security report and remediation manager 220 to report the detected security vulnerability, issue an alert that further advises a solution, and/or execute the appropriate remedial action based on the security vulnerability findings. Remedial actions executed by the security service engine on the selected port can include, but not limited to, stopping the communication of the service on the selected port and/or closing the selected port itself, if necessary.
In some embodiments, security service engine 206 is configured to utilize a SGE security configuration manager 214 to monitor and assess the security configuration of a security gateway element. In some embodiments, SGE security configuration manager 214 is configured to ensure that SGE 106 is in a secure configuration.
In block 506, SGE security configuration manager 214 is configured to issue reports and/or initiate remedial actions. For example, SGE security configuration manager 214 can issue a report detailing a detected unsecured configuration and provide a recommendation regarding the correct security configuration for the interface and/or SGE 106. Additional remedial actions that can be executed by SGE security configuration manager 214 and/or security report and remediation manager 220 include the rejection of a non-secure security configuration or the initiation of an automated repair for a non-secure security configuration on SGE 106.
In some embodiments, security service engine 206 is configured to utilize a network traffic security analysis manager 216 to monitor and assess security vulnerabilities attributed to the network traffic flows that traverse a secure gateway entity. In some embodiments, SSE 206 and/or network traffic security analysis manager 216 is configured to assess the network traffic security of the SGE 106. For example, network traffic security analysis manager 216 can be configured to utilize by existing call analysis methods, such as session initiation protocol (SIP) and call admission control (CAC), to conduct an assessment of the network traffic security existing at SGE 106.
In block 606, network traffic security analysis manager 216 is configured to issue reports and recommend remedial actions. For example, network traffic security analysis manager 216 can instruct security report and remediation manager 220 to issue a report that specifies the security vulnerabilities identified by network traffic security analysis manager 216 and provide a recommendation regarding the correct security configuration for SGE 106. In some embodiments, network traffic security analysis manager 216 and/or security report and remediation manager 220 is configured to automatically reject network traffic packets in the event that the maximum network traffic bandwidth (e.g., bytes/second) that SGE 106 is configured to handle has been reached or exceeded. Additional remedial actions that can be executed by the network traffic security analysis manager 216 and/or security report and remediation manager 220 include the rejection of calls and/or the ceasing of certain network packet traffic.
In some embodiments, security service engine 206 is configured to utilize an analytics security service manager 218 to monitor and assess security vulnerabilities using collected data and statistics. More specifically, analytics security service manager 218 is configured to intelligently conduct a security assessment of the security gateway element through a systematic analysis of data and statistics collected from the operating SGE 106. In some embodiments, analytics security service manager 218 is configured to analyze SGE statistics (e.g., SIP statistics, packet flow statistics, and the like) collected by components and interfaces of the SGE 106, system logs recorded by SGE 106 controller, call detail records (CDRs) generated by SGE 106, simple network management protocol (SNMP) traps and alerts detected by SGE 106, historical data records (HDRs) generated by SGE 106, and the like.
In block 802, a security configuration for a security gateway element (SGE) corresponding to a provisioned security service policy definition is established. In some embodiments, a system administrator provisions a security service policy definition onto the security gateway element via a user interface manager. For example, the security service engine can receive the security service policy definition and establish a security configuration for the security gateway element.
In block 804, a plurality of SGE security service managers hosted by the service security engine on the SGE is configured based on policies included in the security service policy definition. In some embodiments, the security service engine is adapted to assess the policies defined in the security service policy definition to establish and/or update a plurality of SGE security service managers hosted by the security service engine. For example, the security service engine can utilize the policies of the security service policy definition to configure a SGE component security check manager, a network security status manager, a SGE security configuration manager, a network traffic security analysis manager, and the analytics security service manager hosted by the security service engine.
In block 806, each of the plurality of SGE security service managers is executed by the SSE as a software based service in real time to enforce the policies of the security service policy definition on the SGE. In some embodiments, the security service engine is configured to operate on the security gateway element in real time. In particular, the security service engine executes each of the SGE security service managers described above in order to monitor, detect, and prevent potential malicious attacks directed to the security gateway element.
In block 808, the security configuration of the SGE is remediated if one or more of the plurality of SGE security service managers detects a security vulnerability corresponding to the operation of the SGE. In some embodiments, at least one of the security service managers conducts a security assessment on the security gateway element and subsequently detects a system vulnerability in real time. In response to the detected system vulnerability, the security service engine is adapted to initiate a remediation action and/or issue a report. In some embodiments, the security service engine can utilize its security report manager to generate a report message that is sent to a system administrator in order to alert of the detected system vulnerability. In some embodiments, each of the security service managers includes its own security report manager that is configured to issue the reporting action. Likewise, the security service engine is configured to initiate the appropriate remedial action based on the detected security vulnerability.
Advantages of the subject matter described herein include implementing security intelligence into a security gateway element, such as a session border controller, as a service (e.g., software as a service) executed by a security service engine. As such, the security service engine is able to enforce security policies and regulations, issue remediation guidance, and to dynamically detect and prevent potential malicious attacks at run time. Instead of relying on traditional security configuration guides and manually checking hardware and software components, a security gateway element can be assessed, monitored, and remediated in an automated manner when supported by the disclosed security service engine. Notably, the described monitoring and remediation techniques increases the rate at which changes to a security gateway element can be implemented. In addition, such a measure ensures that the security gateway element is assessed for security vulnerabilities in real-time. This can have an enormous impact on the cost of securing an enterprise network supported by the security gateway element as well as the damage inflicted by undetected security breaches. Thus, a security gateway element configured to dynamically remedy itself in such a manner is able to respond to identified security vulnerabilities and/or prevent potential malicious attacks as described herein improves the technological field of computer network security by reducing the likelihood of breaches on computer networks in a more efficient manner.
It will be understood that various details of the presently disclosed subject matter may be changed without departing from the scope of the presently disclosed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.
Number | Name | Date | Kind |
---|---|---|---|
5991879 | Still | Nov 1999 | A |
6473400 | Manning | Oct 2002 | B1 |
6760775 | Anerousis et al. | Jul 2004 | B1 |
6781990 | Puri et al. | Aug 2004 | B1 |
7000247 | Banzhof | Feb 2006 | B2 |
7472422 | Agbabian | Dec 2008 | B1 |
7735116 | Gauvin | Jun 2010 | B1 |
8135823 | Cole | Mar 2012 | B2 |
8553634 | Chun | Oct 2013 | B2 |
8813225 | Fuller | Aug 2014 | B1 |
9117069 | Oliphant | Aug 2015 | B2 |
9325728 | Kennedy | Apr 2016 | B1 |
9608997 | Nicodemus | Mar 2017 | B2 |
9973540 | Li | May 2018 | B2 |
10075466 | Oliphant | Sep 2018 | B1 |
10225288 | Haugsnes | Mar 2019 | B2 |
10454963 | Smith | Oct 2019 | B1 |
10484331 | Rossman | Nov 2019 | B1 |
10567413 | Ahn et al. | Feb 2020 | B2 |
20030069958 | Jalava | Apr 2003 | A1 |
20040003087 | Chambliss | Jan 2004 | A1 |
20040004941 | Malan | Jan 2004 | A1 |
20040025173 | Levonai et al. | Feb 2004 | A1 |
20040054925 | Etheridge | Mar 2004 | A1 |
20050119905 | Wong et al. | Jun 2005 | A1 |
20050154979 | Chidlovskii et al. | Jul 2005 | A1 |
20050198099 | Motsinger et al. | Sep 2005 | A1 |
20060242695 | Nedeltchev | Oct 2006 | A1 |
20070143851 | Nicodemus | Jun 2007 | A1 |
20080151779 | Johnson et al. | Jun 2008 | A1 |
20080219239 | Bell | Sep 2008 | A1 |
20090024663 | McGovern | Jan 2009 | A1 |
20090116573 | Gaal et al. | May 2009 | A1 |
20090119776 | Palnitkar | May 2009 | A1 |
20090154367 | Aaron | Jun 2009 | A1 |
20100020688 | Spatscheck | Jan 2010 | A1 |
20100029626 | Bold | Feb 2010 | A1 |
20100071035 | Budko et al. | Mar 2010 | A1 |
20100306408 | Greenberg | Dec 2010 | A1 |
20110080897 | Hernandez | Apr 2011 | A1 |
20120246730 | Raad | Sep 2012 | A1 |
20120304277 | Li | Nov 2012 | A1 |
20130034022 | Yen et al. | Feb 2013 | A1 |
20130254375 | Agiwal | Sep 2013 | A1 |
20130294230 | Popa | Nov 2013 | A1 |
20130294284 | Popa | Nov 2013 | A1 |
20130298230 | Kumar | Nov 2013 | A1 |
20140082169 | Shinde | Mar 2014 | A1 |
20140281548 | Boyer | Sep 2014 | A1 |
20150040231 | Oliphant et al. | Feb 2015 | A1 |
20150040321 | Moore | Feb 2015 | A1 |
20150135209 | LaBosco | May 2015 | A1 |
20160014159 | Schrecker | Jan 2016 | A1 |
20160182329 | Armolavicius | Jun 2016 | A1 |
20160219048 | Porras | Jul 2016 | A1 |
20170026231 | Poosala | Jan 2017 | A1 |
20170286689 | Kelley | Oct 2017 | A1 |
20180084081 | Kuchibhotla | Mar 2018 | A1 |
20180324203 | Estes | Nov 2018 | A1 |
20180332069 | Moore | Nov 2018 | A1 |
20180351970 | Majumder | Dec 2018 | A1 |
20180352004 | Leung et al. | Dec 2018 | A1 |
20190035027 | Ng et al. | Jan 2019 | A1 |
20190236062 | Proctor | Aug 2019 | A1 |
20190342323 | Henderson | Nov 2019 | A1 |
20200159933 | Ciano | May 2020 | A1 |
20200228560 | Murthy | Jul 2020 | A1 |
20200244517 | Prasad | Jul 2020 | A1 |
20200274902 | Gopal et al. | Aug 2020 | A1 |
20210141351 | Yang et al. | May 2021 | A1 |
Number | Date | Country |
---|---|---|
2929304 | May 2015 | CA |
101227289 | Jul 2008 | CN |
6266696 | Jan 2018 | JP |
2018170803 | Nov 2018 | JP |
WO 20110115856 | Sep 2011 | WO |
WO-2018183313 | Oct 2018 | WO |
WO 2020176174 | Sep 2020 | WO |
Entry |
---|
Barrere, “Vulnerability Management for Safe Configurations in Autonomic Networks and Systems”, 2014 (Year: 2014). |
Laurie, “Managed Vulnerability Assessment (MVA)—Improve Security By Understanding Your Own Vulnerabilities!”, 2002 (Year: 2002). |
Liu et al., “A Practical Vulnerability Assessment Program”, 2007 (Year: 2007). |
Ahmad et al., “Security in Software defined networks: A Survey”, 2015 (Year: 2015). |
Akkaya et al., “Sink repositioning for enhanced performance in wireless sensor networks”, 2005 (Year: 2005). |
Andelman et al., “Competitive Management of Non-preemptive Queues with Multiple Values”, 2003 (Year: 2003). |
Argyraki et al., “Scalable Network-Layer Defense Against Internet Bandwidth-Flooding Attacks”, 2009 (Year: 2009). |
Curnyn, “Optimization of a heterogeneous virtual wireless network”, WO 2003028313 A2, 2003 (Year: 2003). |
Jin et al., “Network Architecture and QoS Issues in the Internet of Things for a Smart City”, 2012 (Year: 2012). |
Kreutz et al., “Software-Defined Networking: A Comprehensive Survey”, 2014 (Year: 2014). |
Kumar et al., “Intrusion Detection System for Grid Computing using SNORT”, 2012 (Year: 2012). |
Mankin, “Gateway congestion control survey”, RFC 1254, 1991 (Year: 1991). |
Merriam-Webster, “remedy”, 2021 (Year: 2021). |
Microsoft Computer Dictionary, “real time”, p. 144, 2002 (Year: 2002). |
Oueslati et al., “A new direction for quality of service: Flow-aware networking”, 2005 (Year: 2005). |
Yang et al., “Admission Control of Integrated Voice/Data Traffic for Networks of Leo Satellites Using CDMA”, 1994 (Year: 1994). |
Non-Final Office Action for U.S. Appl. No. 16/286,508 (dated Nov. 27, 2020). |
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application Serial No. PCT/US2020/021898 (dated Jun. 16, 2020). |
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application Serial No. PCT/US2020/014017 (dated Apr. 23, 2020). |
Commonly-Assigned, co-pending U.S. Appl. No. 16/286,508 for “Methods, Systems, and Computer Readable Media for Dynamically Remediating a Security System Entity,” (Unpublished, filed Feb. 26, 2019). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/286,508 (May 19, 2021). |
Applicant-Initiated Interview Summary for U.S. Appl. No. 16/286,508 (Mar. 15, 2021). |
Number | Date | Country | |
---|---|---|---|
20200296136 A1 | Sep 2020 | US |