Adaptive network security using zero trust microsegmentation
US-2024356980-A1 · Oct 24, 2024 · US
US2016036818A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016036818-A1 |
| Application number | US-201414449859-A |
| Country | US |
| Kind code | A1 |
| Filing date | Aug 1, 2014 |
| Priority date | Aug 1, 2014 |
| Publication date | Feb 4, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In one embodiment, a method includes, by a computing device, receiving identifiers of one or more sessions, users, or groups selected to have access to a particular redirected device. The computing device stores the identifiers in a database, receives a request associated with a session, user, or group to access the particular redirected device, and determines whether an identifier for the session, user, or group associated with the request is stored in the database. If the identifier is stored in the database, then the computing device grants access to the redirected device, or if the identifier is not stored in the database, then the computing device blocks the session, user, or group from accessing the redirected device.
Opening claim text (preview).
What is claimed is: 1 . A method comprising: by a computing device, receiving identifiers of one or more sessions, users, or groups selected to have access to a particular redirected device; by the computing device, storing the identifiers in a database; by the computing device, receiving a request associated with a session, user, or group to access the particular redirected device; by the computing device, determining whether an identifier for the session, user, or group associated with the request is stored in the database; and if the identifier for the session, user, or group associated with the request is stored in the database, then granting the session, user, or group access to the redirected device; or if the identifier for the session, user, or group associated with the request is not stored in the database, then blocking the session, user, or group from accessing the redirected device. 2 . The method of claim 1 , wherein the redirected device comprises a USB device. 3 . The method of claim 1 , wherein the computing device is a server computing device. 4 . The method of claim 1 , wherein a user of the particular redirected device specifies the one or more sessions, users, or groups selected to have access to the particular redirected device. 5 . The method of claim 1 , wherein a filter driver of the computing device grants or blocks access to the redirected device. 6 . The method of claim 5 , wherein the filter driver grants access to the redirected device by moving symbolic links to the redirected device from a global namespace to a local namespace associated with the session, user, or group associated with the request. 7 . The method of claim 5 , wherein the filter driver is associated with a particular class of redirected devices. 8 . One or more computer-readable non-transitory storage media embodying software that is operable when executed to: receive identifiers of one or more sessions, users, or groups selected to have access to a particular redirected device; store the identifiers in a database; receive a request associated with a session, user, or group to access the particular redirected device; determine whether an identifier for the session, user, or group associated with the request is stored in the database; and if the identifier for the session, user, or group associated with the request is stored in the database, then grant the session, user, or group access to the redirected device; or if the identifier for the session, user, or group associated with the request is not stored in the database, then block the session, user, or group from accessing the redirected device. 9 . The media of claim 8 , wherein the redirected device comprises a USB device. 10 . The media of claim 8 , wherein a server computing device comprises the media. 11 . The media of claim 8 , wherein a user of the particular redirected device specifies the one or more sessions, users, or groups selected to have access to the particular redirected device. 12 . The media of claim 8 , wherein a filter driver grants or blocks access to the redirected device. 13 . The media of claim 12 , wherein the filter driver grants access to the redirected device by moving symbolic links to the redirected device from a global namespace to a local namespace associated with the session, user, or group associated with the request. 14 . The media of claim 12 , wherein the filter driver is associated with a particular class of redirected devices. 15 . A system comprising: one or more processors; and a memory coupled to the processors comprising instructions executable by the processors, the processors being operable when executing the instructions to: receive identifiers of one or more sessions, users, or groups selected to have access to a particular redirected device; store the identifiers in a database; receive a request associated with a session, user, or group to access the particular redirected device; determine whether an identifier for the session, user, or group associated with the request is stored in the database; and if the identifier for the session, user, or group associated with the request is stored in the database, then grant the session, user, or group access to the redirected device; or if the identifier for the session, user, or group associated with the request is not stored in the database, then block the session, user, or group from accessing the redirected device. 16 . The system of claim 15 , wherein the redirected device comprises a USB device. 17 . The system of claim 15 , wherein a user of the particular redirected device specifies the one or more sessions, users, or groups selected to have access to the particular redirected device. 18 . The system of claim 15 , wherein a filter driver grants or blocks access to the redirected device. 19 . The system of claim 18 , wherein the filter driver grants access to the redirected device by moving symbolic links to the redirected device from a global namespace to a local namespace associated with the session, user, or group associated with the request. 20 . The system of claim 18 , wherein the filter driver is associated with a particular class of redirected devices.
Grouping of entities · CPC title
Entity profiles · CPC title
Access control lists [ACL] · CPC title
for controlling access to devices or network resources · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.