System for monitoring and managing datacenters

US11936663B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11936663-B2
Application numberUS-202218054069-A
CountryUS
Kind codeB2
Filing dateNov 9, 2022
Priority dateJun 5, 2015
Publication dateMar 19, 2024
Grant dateMar 19, 2024

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An example method includes detecting, using sensors, packets throughout a datacenter. The sensors can then send packet logs to various collectors which can then identify and summarize data flows in the datacenter. The collectors can then send flow logs to an analytics module which can identify the status of the datacenter and detect an attack.

First claim

Opening claim text (preview).

What is claimed is: 1. A system comprising: one or more processors; and memory storing instructions which, when executed by the one or more processors, cause the one or more processors to: obtain network data from sensor processes executing in a data center, the network data being at least partly based on operation system states associated with an operating system in the data center; store connection data describing a connection between endpoints associated with one or more packets transmitted in the data center; determine a status of the data center based on the network data and the connection data; detect, based at least partly on the status of the data center, an indication of an attack within the data center; and in response to the indication of the attack, modify a security policy based on the status of the data center. 2. The system of claim 1 , wherein the network data comprises a respective indication of active or previously active processes on each of the operating system. 3. The system of claim 1 , wherein at least one of a log or the network data identifies files present on the operating system. 4. The system of claim 1 , wherein at least one of a log or the network data comprises data describing packets captured by the sensor processes executing in the data center. 5. The system of claim 1 , wherein the operating system is a virtual machine or a hypervisor. 6. The system of claim 1 , wherein detecting the indication of the attack comprises at least one of detecting a spike in an amount of resources used by at least one of the sensor processes or detecting spoofed packets. 7. The system of claim 1 , wherein detecting the indication of the attack comprises detecting a hidden process embedded in traffic between two or more reference points. 8. The system of claim 1 , wherein detecting the indication of the attack comprises detecting a scan of a network as initiated by a command from outside of the network or from an unexpected source inside the network. 9. The system of claim 1 , wherein detecting the indication of the attack comprises detecting a packet that has a packet header field that differs from an expected header pattern. 10. A method comprising: obtaining network data from sensor processes executing in a data center, the network data being at least partly based on operation system states associated with an operating system in the data center; storing connection data describing a connection between endpoints associated with one or more packets in the network data; determining a status of the data center based on the network data and the connection data; detecting, based at least partly on the status of the data center, an indication of an attack within the data center; and in response to the indication of the attack, modifying a security policy based on the status of the data center. 11. The method of claim 10 , wherein at least one of a log or the network data comprises a respective indication of active or previously active processes on each of the operating system. 12. The method of claim 10 , wherein at least one of a log or the network data identifies files present on the operating system. 13. The method of claim 10 , wherein at least one of a log or the network data comprises data describing packets captured by the sensor processes executing in the data center. 14. The method of claim 10 , wherein the operating system comprises a virtual machine or a hypervisor. 15. The method of claim 10 , wherein detecting the indication of the attack comprises at least one of detecting a spike in an amount of resources used by at least one of the sensor processes or detecting spoofed packets. 16. The method of claim 10 , wherein detecting the indication of the attack comprises detecting a hidden process embedded in traffic between two or more reference points. 17. The method of claim 10 , wherein detecting the indication of the attack comprises detecting a scan of a network as initiated by a command from outside of the network or from an unexpected source inside the network. 18. A non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by one or more processors, cause the one or more processors to: obtain network data from sensor processes executing in a data center, the network data being at least partly based on operation system states associated with an operating system in the data center; store connection data describing a connection between endpoints associated with one or more packets transmitted in the data center; determine a status of the data center based on the network data and the connection data; detect, based at least partly on the status of the data center, an indication of an attack within the data center; and in response to the indication of the attack, modify a security policy based on the status of the data center. 19. The non-transitory computer-readable medium of claim 18 , wherein at least one of a log or the network data comprises a respective indication of active or previously active processes on each of the operating system. 20. The non-transitory computer-readable medium of claim 18 , wherein at least one of a log or the network data comprises at least one of information about files present on the operating system or information describing packets captured by the sensor processes executing in the data center.

Assignees

Inventors

Classifications

  • by monitoring network traffic (monitoring network traffic per se H04L43/00) · CPC title

  • H04L43/04Primary

    Processing captured monitoring data, e.g. for logfile generation · CPC title

  • Packet rate · CPC title

  • for separating internal from external traffic, e.g. firewalls · CPC title

  • Traffic logging, e.g. anomaly detection · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11936663B2 cover?
An example method includes detecting, using sensors, packets throughout a datacenter. The sensors can then send packet logs to various collectors which can then identify and summarize data flows in the datacenter. The collectors can then send flow logs to an analytics module which can identify the status of the datacenter and detect an attack.
Who is the assignee on this patent?
Cisco Tech Inc
What technology area does this patent fall under?
Primary CPC classification H04L63/1408. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Mar 19 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).