IP Library › Granted Patent US 12,513,167
Granted Patent B2
US 12,513,167 · App. 18/674,385 · Granted Dec 30, 2025

Adaptive security architecture based on state of posture

Inventor: Jonathan J. Thompson (Carmel, IN)
Assignee: AS0001, Inc.
H04L63/1416H04L63/1425H04L63/1433H04L63/1441H04L63/20
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,513,167
App. No.
18/674,385
Granted
Dec 30, 2025
Kind
B2
Abstract

Systems, methods, and computer-readable storage media for protecting data. One system includes one or more processing circuits configured to identify parameters for protecting an entity, wherein the parameters correspond with proof of entity security postures. The processing circuits are further configured to generate one or more plans corresponding with the parameters for protecting, wherein generating includes activating a tool within a computing infrastructure of the entity. The processing circuits are further configured to monitor entity data with the tool activated corresponding with the plans, generate an order, incident, or protection plan based on a detection from monitoring the entity data or at least one interaction with a marketplace, and provide the order, incident, or protection plan to a third party.

Claims (65)

1 . A data protection system, comprising:

one or more processing circuits comprising executable instructions to:

receive an input from an entity of a plurality of entities via an interface, the interface comprising a plurality of protection plans for protecting a computing infrastructure of the entity;

identify, based on the input, parameters for protecting the entity corresponding with a third-party, wherein the parameters for protecting correspond with proof of one or more security postures of the entity, the one or more security postures representing (i) a state of cyber resilience of the computing infrastructure to one or more cybersecurity threats and (ii) one or more indexes, pointers, or references to data or resources of the computing infrastructure;

generate one or more protection plans of the plurality of protection plans corresponding with the parameters for protecting, wherein generating the one or more protection plans comprises activating a tool within the computing infrastructure of the entity based on the parameters for protecting;

monitor entity data of the entity with the tool activated corresponding with the one or more protection plans;

generate an order, incident, or protection plan based on a detection from monitoring the entity data or at least one interaction with a marketplace; and

provide the order, incident, or protection plan to an interface of a third-party computing system of the third-party as a plurality of actions, and wherein at least one of the plurality of actions comprises cybersecurity data corresponding with the one or more security postures of the entity.

2 . The data protection system of claim 1 , wherein the one or more processing circuits are further configured to:

provide the one or more protection plans to the marketplace for activation by the plurality of entities; and

receive, from an entity computing system, an activation of the one or more protection plans;

wherein the one or more protection plans comprise one or more of a cybersecurity plan, an insurance plan, or the protection plan.

3 . The data protection system of claim 2 , wherein the one or more processing circuits are further configured to:

generate and activate a cybersecurity protection obligation between the entity and the third-party, wherein the cybersecurity protection obligation comprises a plurality of a protection attributes; and

provide the one or more security postures, the entity data of the entity, and the cybersecurity protection obligation to the third-party computing system of the third-party.

4 . The data protection system of claim 1 , wherein the one or more processing circuits are further configured to:

wrap and provide, to an application programming interface (API), the parameters for protection.

5 . The data protection system of claim 1 , wherein the one or more processing circuits are further configured to:

automatically renew at least one of the one or more protection plans with at least one of the plurality of entities.

6 . The data protection system of claim 1 , wherein the one or more processing circuits are further configured to:

in response to receiving an indication of a completion of the incident, automatically generate and provide an invoice of the order, incident, or protection plan to the entity; and

in response to the completion of the incident, generate an incident summary comprising at least performance metrics, origination details of the incident, and an incident timeline.

7 . The data protection system of claim 1 , wherein generating the incident comprises generating a plurality of action items, and wherein the one or more processing circuits are further configured to:

prior to generating the one or more protection plans, provide the one or more protection plans to at least one of the plurality of entities for purchase based on one or more third-party customer parameters.

8 . The data protection system of claim 1 , wherein the one or more processing circuits are further configured to:

receive or determine one or more partners of the third-party; and

configure one or more routing rules for automatically sending action items in response to receiving the order, incident, or protection plan.

9 . The data protection system of claim 1 , wherein:

the incident is categorized into at least one of an inbound incident, an active incident, or a past incident, and the inbound incident comprise the cybersecurity data associated with the entity, and the active incident comprise real-time statuses and states;

wherein the interface of the third-party computing system comprises an incident room for a plurality of active incidents.

10 . The data protection system of claim 1 , wherein the one or more processing circuits are further configured to deploy and configure the tool within the computing infrastructure of the entity based on one or more requirements outlined in the one or more protection plans, wherein deploying comprises installing the tool within the computing infrastructure of the entity, and wherein configuring comprises modifying one or more settings or parameters of the tool within the computing infrastructure of the entity that aligns with the one or more protection plans.

11 . The data protection system of claim 10 , wherein generating and activating the one or more protection plans further comprises establishing connections and integrating the tool with the computing infrastructure of the entity, and wherein deploying further comprises at least one of (1) installing one or more software agents on endpoints of the computing infrastructure, (2) installing network appliances or sensors within the computing infrastructure, or (3) provisioning virtual instances of the tool in a cloud environment of the computing infrastructure.

12 . A method for protecting data, comprising:

receiving, by one or more processing circuits, an input from an entity of a plurality of entities via an interface, the interface comprising a plurality of protection plans for protecting a computing infrastructure of the entity;

identifying, by one or more processing circuits, based on the input, parameters for protecting the entity corresponding with a third-party, wherein the parameters for protection correspond with proof of one or more security postures of the entity, the one or more security postures representing (i) a state of cyber resilience of the computing infrastructure to one or more cybersecurity threats and (ii) one or more indexes, pointers, or references to data or resources of the computing infrastructure;

generating, by the one or more processing circuits, one or more protection plans of the plurality of protection plans corresponding with the parameters for protecting, wherein generating the one or more protection plans comprises activating a tool within the computing infrastructure of the entity based on the parameters for protecting;

monitoring, by the one or more processing circuits, entity data of the entity with the tool activated corresponding with the one or more protection plans;

generating, by the one or more processing circuits, an order, incident, or protection plan based on detecting from monitoring the entity data or at least one interaction with a marketplace; and

providing, by the one or more processing circuits, the order, incident, or protection plan to an interface of a third-party computing system of the third-party as a plurality of actions, and wherein at least one of the plurality of actions comprises cybersecurity data corresponding with the one or more security postures of the entity.

13 . The method of claim 12 , further comprising:

providing, by the one or more processing circuits, the one or more protection plans to the marketplace for activation by the plurality of entities; and

receiving, by the one or more processing circuits from an entity computing system, an activation of the one or more protection plans;

wherein the one or more protection plans comprise or more of a cybersecurity plan, an insurance plan, or the protection plan.

14 . The method of claim 13 , further comprising:

generating and activating, by the one or more processing circuits, a cybersecurity protection obligation between the entity and the third-party, wherein the cybersecurity protection obligation comprises a plurality of a protection attributes; and

providing, by the one or more processing circuits, the one or more security postures, the entity data of the entity, and the cybersecurity protection obligation to the third-party computing system of the third-party.

15 . The method of claim 12 , further comprising:

wrapping and providing, by the one or more processing circuits to an application programming interface (API), the parameters for protecting.

16 . The method of claim 12 , further comprising:

automatically renewing, by the one or more processing circuits, at least one of the one or more protection plans with at least one of the plurality of entities.

17 . The method of claim 12 , further comprising:

in response to receiving an indication of a completion of the incident, automatically generating and providing, by the one or more processing circuits, an invoice of the incident to the entity; and

in response to the completion of the incident, generating, by the one or more processing circuits, an incident summary comprising at least performance metrics, origination details of the incident, and an incident timeline.

18 . The method of claim 12 , wherein generating the incident comprises generating a plurality of action items, and further comprising:

prior to generating the one or more protection plans, providing, by the one or more processing circuits, the one or more protection plans to at least one of the plurality of entities for purchase based on one or more third-party customer parameters.

19 . The method of claim 12 , further comprising:

receiving or determining, by the one or more processing circuits, one or more partners of the third-party; and

configuring, by the one or more processing circuits, one or more routing rules for automatically sending action items in response to receiving the order, incident, or protection plan.

20 . A non-transitory computer readable medium (CRM) comprising one or more instructions stored thereon and executable by one or more processors to:

receive an input from an entity of a plurality of entities via an interface, the interface comprising a plurality of protection plans for protecting a computing infrastructure of the entity;

identify, based on the input, parameters for protecting the entity corresponding with a third-party, wherein the parameters for protecting correspond with proof of one or more security postures of the entity, the one or more security postures representing (i) a state of cyber resilience of the computing infrastructure to one or more cybersecurity threats and (ii) one or more indexes, pointers, or references to data or resources of the computing infrastructure;

generate one or more protection plans of the plurality of protection plans corresponding with the parameters for protecting, wherein generating the one or more protection plans comprises activating a tool within the computing infrastructure of the entity based on the parameters for protecting;

monitor entity data of the entity with the tool activated corresponding with the one or more protection plans;

generate an order, incident, or protection plan based on a detection from monitoring the entity data or at least one interaction with a marketplace; and

provide the order, incident, or protection plan to an interface of a third-party computing system of the third-party as a plurality of actions, and wherein at least one of the plurality of actions comprises cybersecurity data corresponding with the one or more security postures of the entity.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 3, 2024
From: THOMPSON, JONATHAN J.
To: AS0001, INC.
Reel/Frame 067595/0511 →
Continuity (4)
Continuation 18326715 · May 31, 2023
Provisional Application 63457671 · Apr 6, 2023
Provisional Application 63347389 · May 31, 2022
Related Publication 20240314149A1 · Sep 19, 2024
References Cited (201)
US 7592829B2 · Walmsley et al. · 2009 [cited by applicant]
US D653258S · Cahill et al. · 2012 [cited by applicant]
US 8166314B1 · Raizen et al. · 2012 [cited by applicant]
US 8316237B1 · Felsher et al. · 2012 [cited by applicant]
US 10003584B1 · Roth et al. · 2018 [cited by applicant]
US 10102587B1 · Potter et al. · 2018 [cited by applicant]
US 10135862B1 · Mcclintock et al. · 2018 [cited by applicant]
US 10438001B1 · Hariprasad · 2019 [cited by applicant]
US 10565534B2 · Delacourt et al. · 2020 [cited by applicant]
US 10728019B2 · Winslow et al. · 2020 [cited by applicant]
US 10732962B1 · Florescu · 2020 [cited by applicant]
US 10785255B1 · Otvagin et al. · 2020 [cited by applicant]
US 11023585B1 · Light et al. · 2021 [cited by applicant]
US 11057426B2 · Davis · 2021 [cited by applicant]
US 11089047B1 · Kaushal · 2021 [cited by examiner]
US 11122073B1 · Cai et al. · 2021 [cited by applicant]
US 11128457B2 · Murdoch et al. · 2021 [cited by applicant]
US 11188896B1 · Hertzog et al. · 2021 [cited by applicant]
US 11233647B1 · Fontaine · 2022 [cited by applicant]
US 11240275B1 · Vashisht et al. · 2022 [cited by applicant]
US 11244261B2 · To et al. · 2022 [cited by applicant]
US 11354430B1 · Tharakan et al. · 2022 [cited by applicant]
US 11470106B1 · Lin et al. · 2022 [cited by applicant]
US 11477208B1 · Ureã±a et al. · 2022 [cited by applicant]
US 11501379B2 · Teresi · 2022 [cited by applicant]
US 11503061B1 · Lin et al. · 2022 [cited by applicant]
US 11550907B2 · Silberman et al. · 2023 [cited by applicant]
US 11568455B2 · Hogg et al. · 2023 [cited by applicant]
US 11587177B2 · Sankar et al. · 2023 [cited by applicant]
US 11620390B1 · Stone et al. · 2023 [cited by applicant]
US 11681811B1 · Dixit · 2023 [cited by applicant]
US 11729204B1 · Coull et al. · 2023 [cited by applicant]
US 11750643B1 · Imrem et al. · 2023 [cited by applicant]
US 11757923B1 · Vandeventer et al. · 2023 [cited by applicant]
US 11777992B1 · Cross et al. · 2023 [cited by applicant]
US 11783052B2 · Light et al. · 2023 [cited by applicant]
US 11783062B2 · Lounsberry · 2023 [cited by applicant]
US 11811818B1 · Vandeventer et al. · 2023 [cited by applicant]
US 11816223B1 · Vandeventer et al. · 2023 [cited by applicant]
US 11818120B2 · Jen et al. · 2023 [cited by applicant]
US 11824881B2 · Shaw et al. · 2023 [cited by applicant]
US 11824888B1 · Vandeventer et al. · 2023 [cited by applicant]
US 11838300B1 · Vashisht · 2023 [cited by examiner]
US 11870799B1 · Imrem et al. · 2024 [cited by applicant]
US 11870812B2 · Li · 2024 [cited by applicant]
US 11888886B1 · Kudale et al. · 2024 [cited by applicant]
US 11893121B1 · Imrem et al. · 2024 [cited by applicant]
US 11895141B1 · Vandeventer et al. · 2024 [cited by applicant]
US 11909757B2 · Kibler et al. · 2024 [cited by applicant]
US 11924237B2 · Evans · 2024 [cited by applicant]
US 11943254B2 · Thompson · 2024 [cited by applicant]
US 12008332B1 · Gardner et al. · 2024 [cited by applicant]
US 12107869B1 · Kannan et al. · 2024 [cited by applicant]
US 12126995B2 · Hua et al. · 2024 [cited by applicant]
US 12169569B2 · Belfiore, Jr. et al. · 2024 [cited by applicant]
US 12182853B1 · Haider · 2024 [cited by examiner]
US 12328340B2 · Hamill · 2025 [cited by examiner]
US 20070008098A1 · Wong · 2007 [cited by applicant]
US 20090076879A1 · Sparks et al. · 2009 [cited by applicant]
US 20120130874A1 · Mane et al. · 2012 [cited by applicant]
US 20130304616A1 · Raleigh et al. · 2013 [cited by applicant]
US 20140136379A1 · Smith et al. · 2014 [cited by applicant]
US 20140279352A1 · Schaefer et al. · 2014 [cited by applicant]
US 20150019658A1 · Barrera · 2015 [cited by examiner]
US 20150163206A1 · Mccarthy et al. · 2015 [cited by applicant]
US 20160019636A1 · Adapalli et al. · 2016 [cited by applicant]
US 20160070908A1 · Sanghvi et al. · 2016 [cited by applicant]
US 20160110819A1 · Sankar et al. · 2016 [cited by applicant]
US 20160132806A1 · To et al. · 2016 [cited by applicant]
US 20160218875A1 · Le Saint et al. · 2016 [cited by applicant]
US 20170041296A1 · Ford et al. · 2017 [cited by applicant]
US 20170063910A1 · Muddu et al. · 2017 [cited by applicant]
US 20170187742A1 · Rogers et al. · 2017 [cited by applicant]
US 20170214632A1 · Vedula · 2017 [cited by applicant]
US 20180146004A1 · Belfiore et al. · 2018 [cited by applicant]
US 20180248901A1 · Rieke · 2018 [cited by examiner]
US 20180316695A1 · Esman · 2018 [cited by examiner]
US 20180322292A1 · Tedeschi · 2018 [cited by examiner]
US 20180367310A1 · Leong et al. · 2018 [cited by applicant]
US 20190052664A1 · Kibler · 2019 [cited by examiner]
US 20190095320A1 · Biswas et al. · 2019 [cited by applicant]
US 20190098037A1 · Shenoy et al. · 2019 [cited by applicant]
US 20190130113A1 · Obermeier et al. · 2019 [cited by applicant]
US 20190182287A1 · Hanley et al. · 2019 [cited by applicant]
US 20190207966A1 · Vashisht et al. · 2019 [cited by applicant]
US 20190207981A1 · Sweeney · 2019 [cited by examiner]
US 20190230129A1 · Digiambattista et al. · 2019 [cited by applicant]
US 20190236661A1 · Hogg · 2019 [cited by examiner]
US 20190319940A1 · Hamel et al. · 2019 [cited by applicant]
US 20190377712A1 · Miller et al. · 2019 [cited by applicant]
US 20200036707A1 · Callahan et al. · 2020 [cited by applicant]
US 20200067779A1 · Jost et al. · 2020 [cited by applicant]
US 20200195621A1 · Li et al. · 2020 [cited by applicant]
US 20200382547A1 · Basballe Sorensen · 2020 [cited by examiner]
US 20200401696A1 · Ringlein et al. · 2020 [cited by applicant]
US 20200402179A1 · Teresi · 2020 [cited by applicant]
US 20200412751A1 · Thayer et al. · 2020 [cited by applicant]
US 20210029156A1 · Sharifi Mehr · 2021 [cited by applicant]
US 20210035116A1 · Berrington · 2021 [cited by examiner]
US 20210075821A1 · Chenette et al. · 2021 [cited by applicant]
US 20210084057A1 · Chhabra · 2021 [cited by applicant]
US 20210105294A1 · Kruse et al. · 2021 [cited by applicant]
US 20210136121A1 · Crabtree et al. · 2021 [cited by applicant]
US 20210185063A1 · Park et al. · 2021 [cited by applicant]
US 20210201229A1 · Moon et al. · 2021 [cited by applicant]
US 20210209079A1 · Lynch et al. · 2021 [cited by applicant]
US 20210211452A1 · Patel et al. · 2021 [cited by applicant]
US 20210232687A1 · Sasaki et al. · 2021 [cited by applicant]
US 20210234702A1 · Bekiyants · 2021 [cited by applicant]
US 20210234885A1 · Campbell · 2021 [cited by applicant]
US 20210248514A1 · Cella et al. · 2021 [cited by applicant]
US 20210264054A1 · Anson et al. · 2021 [cited by applicant]
US 20210287299A1 · Tofte et al. · 2021 [cited by applicant]
US 20210314293A1 · Soundararajan et al. · 2021 [cited by applicant]
US 20210334386A1 · AlGhamdi · 2021 [cited by examiner]
US 20210342836A1 · Cella et al. · 2021 [cited by applicant]
US 20210344513A1 · Russell et al. · 2021 [cited by applicant]
US 20210357927A1 · Kita et al. · 2021 [cited by applicant]
US 20210360016A1 · Kaushal · 2021 [cited by examiner]
US 20210367963A1 · Murray et al. · 2021 [cited by applicant]
US 20210367964A1 · Jones et al. · 2021 [cited by applicant]
US 20220012333A1 · Tahara · 2022 [cited by applicant]
US 20220027828A1 · Avala et al. · 2022 [cited by applicant]
US 20220036302A1 · Cella et al. · 2022 [cited by applicant]
US 20220060499A1 · Huda · 2022 [cited by applicant]
US 20220094596A1 · Jagannathan et al. · 2022 [cited by applicant]
US 20220156249A1 · Luedtke et al. · 2022 [cited by applicant]
US 20220164440A1 · Murphy et al. · 2022 [cited by applicant]
US 20220198563A1 · Kaplan et al. · 2022 [cited by applicant]
US 20220255969A1 · Cage et al. · 2022 [cited by applicant]
US 20220276996A1 · Gaur et al. · 2022 [cited by applicant]
US 20220329630A1 · Li · 2022 [cited by applicant]
US 20220366494A1 · Cella et al. · 2022 [cited by applicant]
US 20220377099A1 · Berger et al. · 2022 [cited by applicant]
US 20230021214A1 · Lehmer · 2023 [cited by examiner]
US 20230123322A1 · Cella · 2023 [cited by examiner]
US 20230130649A1 · Schwartz et al. · 2023 [cited by applicant]
US 20230171292A1 · Crabtree et al. · 2023 [cited by applicant]
US 20230244794A1 · Vadala · 2023 [cited by examiner]
US 20230259632A1 · Marciano · 2023 [cited by examiner]
US 20230269625A1 · Raleigh et al. · 2023 [cited by applicant]
US 20230308474A1 · Thompson · 2023 [cited by applicant]
US 20230351026A1 · Cross et al. · 2023 [cited by applicant]
US 20230370452A1 · Mannengal · 2023 [cited by examiner]
US 20230379346A1 · Goldstein et al. · 2023 [cited by applicant]
US 20230388324A1 · Thompson · 2023 [cited by applicant]
US 20230403154A1 · Kaizer et al. · 2023 [cited by applicant]
US 20240013198A1 · Terborg et al. · 2024 [cited by applicant]
US 20240039954A1 · Shete et al. · 2024 [cited by applicant]
US 20240064176A1 · Raleigh et al. · 2024 [cited by applicant]
US 20240086918A1 · Gisolfi et al. · 2024 [cited by applicant]
US 20240091646A1 · Mcdonnell · 2024 [cited by applicant]
US 20240104521A1 · Azgad-Tromer et al. · 2024 [cited by applicant]
US 20240121259A1 · Imrem et al. · 2024 [cited by applicant]
US 20240129318A1 · Vandeventer et al. · 2024 [cited by applicant]
US 20240137772A1 · Eaton et al. · 2024 [cited by applicant]
US 20240152645A1 · Blaikie et al. · 2024 [cited by applicant]
US 20240171614A1 · Crabtree et al. · 2024 [cited by applicant]
US 20240184659A1 · Vandeventer et al. · 2024 [cited by applicant]
US 20240185191A1 · Bernardi · 2024 [cited by applicant]
US 20240202221A1 · Siebel et al. · 2024 [cited by applicant]
US 20240256525A1 · Manamohan et al. · 2024 [cited by applicant]
US 20240281472A1 · Larhette et al. · 2024 [cited by applicant]
US 20240289095A1 · Gabay et al. · 2024 [cited by applicant]
US 20240289362A1 · Williams et al. · 2024 [cited by applicant]
US 20240289396A1 · Chrysanthou · 2024 [cited by applicant]
US 20240289408A1 · Chrysanthou · 2024 [cited by applicant]
US 20240289410A1 · Chrysanthou · 2024 [cited by applicant]
US 20240289411A1 · Chrysanthou · 2024 [cited by applicant]
US 20240289535A1 · Murphy et al. · 2024 [cited by applicant]
US 20240289596A1 · Williams et al. · 2024 [cited by applicant]
US 20240289712A1 · Krishnaiah · 2024 [cited by applicant]
US 20240289851A1 · Williams et al. · 2024 [cited by applicant]
US 20240296258A1 · Suto et al. · 2024 [cited by applicant]
US 20240296314A1 · Singh et al. · 2024 [cited by applicant]
US 20240296315A1 · Singh et al. · 2024 [cited by applicant]
US 20240296316A1 · Singh et al. · 2024 [cited by applicant]
US 20240296352A1 · Yanosy et al. · 2024 [cited by applicant]
US 20240296425A1 · Rosenkranz et al. · 2024 [cited by applicant]
US 20240296753A1 · Gogin et al. · 2024 [cited by applicant]
US 20240370854A1 · Williams et al. · 2024 [cited by applicant]
US 20240380621A1 · Mee · 2024 [cited by applicant]
US 20250080567A1 · Thompson · 2025 [cited by applicant]
US 20250202926A1 · Chandrabose · 2025 [cited by examiner]
CA 3131208A1 · 2023 [cited by applicant]
EP 3179696A1 · 2017 [cited by applicant]
WO WO2008147400A1 · 2008 [cited by applicant]
WO WO2019051166A1 · 2019 [cited by applicant]
WO WO2020189926A1 · 2020 [cited by applicant]
WO WO2021105626A1 · 2021 [cited by applicant]
Ahmed et al., “Blockchain-Based Identity Management System and Self-Sovereign Identity Ecosystem: A Comprehensive Survey”, IEEE Access, date of publication Oct. 25, 2022, date of current version Nov. 3, 2022. [cited by applicant]
Fayzullajon et al., “Stages of Processing an Information Security Incident,” 2021 International Conference on Information Science and Communications Technologies (ICISCT) Year: 2021 | Conference Paper | Publisher: IEEE. [cited by applicant]
Foreign Action other than Search Report on GB 2406664.9 Dtd Sep. 9, 2024. [cited by applicant]
International Search Report and Written opinion on PCT/US2024/045448 Dtd Nov. 14, 2024 16 pages. [cited by applicant]
Krivo et al., “The Experience of Cyberthreats Analysis Using Business Intelligence System,” 2020 Ural Symposium on Biomedical Engineering, Radioelectronics and Information Technology (USBEREIT) Year: 2020 | Conference P… [cited by applicant]
International Search Report and Written Opinion for PCT/US2024/023262 dated Jul. 26, 2024, 8 pgs. [cited by applicant]
Examination Report for UK App. No. 2406661.5 dated Nov. 12, 2024, 5 pgs. [cited by applicant]
Achleitner, Stefan et al. MLSNet: A Policy Complying Multilevel Security Framework for Software Defined Networking. IEEE Transactions on Network and Service Management, vol. 18, Issue: 1.https://ieeexplore.ieee.org/stam… [cited by applicant]
Dauch, Kevin et al. Information Assurance Using a Defense In-Depth Strategy. 2009 Cybersecurity Applications & Technology Conference for Homeland Security. https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=S&arnumber=48044… [cited by applicant]
Park, So-Hyun et al. Performance Evaluation of Open-Source Endpoint Detection and Response Combining Google Rapid Response and Osquery for Threat Detection. IEEE Access, vol. 10. https://ieeexplore.ieee.org/stamp/stamp.… [cited by applicant]
Ahmed et al., “Blockchain-Based Identity Management System and Self-Sovereign Identity Ecosystem: A Comprehensive Survey”, IEEE Access, date of publication Oct. 25, 2022, date of current version Nov. 3, 2022. 46 pgs. [cited by applicant]