Systems and methods for security verification

Abstract

Systems are presented for security verification. A security verification system receives an indication of anticipated data exchange between a first content system and a second content system. Based on the indication, the security verification system retrieves security profiles associated with the first and second content systems. The security profiles include security requirements associated with the first content system and security specifications associated with the second content system. The security verification system determines whether the security specifications of the second content system meet the security requirements of the first content system. Based on the determination, a security approval indication or a security denial indication is sent to the first content system. In some embodiments, an agentic system deploys a plurality of agents to autonomously query content systems for security data, compare findings between agents and pass verification results to a processing system that scores the findings against applicable security standards.

Description

SYSTEMS AND METHODS FOR SECURITY VERIFICATIONCross-Reference to Related

[0001] The present application claims priority to U.S. Provisional Application No. 63 / 772,415 filed on March 14, 2025, and entitled, Systems and Methods for Security Verification, the entire disclosure of which is incorporated herein.

[0002] The present disclosure relates to security systems and, more particularly, to evaluating and verifying security methodologies meet certain requirements.Summary

[0003] Security compliance frameworks have emerged as a response to increasing needs to standardized security practices across digital industries and handling risk associated with sensitive data. As digital applications began storing financial records, healthcare information, user data, and other personally identifiable information (PII) in local or online databases, cybersecurity threats have also evolved in parallel, leading to frequent data breaches and regulatory concerns. These digital applications needed standardized guidelines to direct the implementation of security measures that would protect the applications against unauthorized access, data leaks, and other forms of cyberattacks. In response to the needs for standardized security practices, regulatory groups developed frameworks like ISO 27001 (for information security management), SOC 2 (for security provider security), HIPAA (for healthcare data protection), PCI DSS (for payment security), and the General Data Protection Regulation (GDPR) to establish universal security and / or data protection baselines. These frameworks ensured that digital applications were not only securing their data but also demonstrating accountability to users, partners, and regulators. Over time, the scope of compliance expanded beyond basic data protection to address cloud security, third-party risk, and continuous monitoring, reflecting the evolving nature of digital threats.

[0004] In some approaches to ensure that a digital application is compliant towards the aforementioned cybersecurity standards, a compliance application may be used to generate a compliance report regarding the digital application to show that the processing and storing ofaccount data within the digital application is safe and secure, according to the cybersecurity standards. In such approaches, the compliance application may indicate compliance progresses of the digital application. For example, the compliance application may determine that only 48 out of all 130 of security controls related to SOC 2 are in compliance. The compliance application may display a percentage (e.g., 37%) in the compliance report for the progress of becoming compliant to SOC 2. Likewise, the compliance application may determine the percentage of controls for other regulations such as ISO 27001 :2013, ISO 27001 :2022, HIPAA, GDPR, US Data Privacy, NIST Cybersecurity Frameworks, PCLDSS 4.0, ISO 27701, and other forms of regulatory best practices, among others. However, this approach only indicates whether a digital application is compliant towards a regulatory standard and is deficient in providing indications of which security capabilities the digital application has deployed to fulfill certain security requirements.

[0005] In other approaches, application programming interfaces (APIs) are used to determine which security tools are being used by a digital platform. In yet other approaches, A2A (Agent-to-Agent), agentic Al to API, and / or direct connections to systems are used to communicate between systems. Security tools such as Amazon Web Services Security Hub, CrowdStrike, and lira may be integrated into a digital platform. A compliance application may utilize APIs to collect and analyze security data from digital platforms in order to verify security compliance. These APIs provide a direct method for retrieving evidence from cloud service providers, identity and access management systems, security monitoring tools, and other infrastructure components. The compliance application may initiate API requests to integrated systems to access security controls, monitor access permissions, track security events, verify encryption policies, and enable other security measures, among others.

[0006] In one example approach, the compliance application may establish a secure API connection with cloud service providers such as Amazon Web Services (AWS), Google Cloud Platform (GCP), or Microsoft Azure to retrieve security configuration settings. The application may issue API calls to extract data related to identity access and management (IAM), encryption policies, network security settings, and logging configurations, among others. The API responses may be processed to determine whether critical security controls, such as multifactor authentication (MFA) enforcement, least privilege access policies, and storage encryption, among others, are properly implemented. If the compliance application detects a misconfiguration, such as a publicly accessible cloud storage bucket or an inactive user account with administrative privileges, it may generate a non-compliance alert for remediation.

[0007] In yet another example approach, the compliance application may integrate with IAM platforms such as Okta, Microsoft Entra ID, or Google Workspace, among others. By making API calls to retrieve user authentication configurations, access control policies, and privilege assignment records, the compliance application may determine whether access management controls are aligned with the aforementioned compliance frameworks. For example, if an IAM API response indicates that a privileged user account lacks MFA protection, or an inactive user remains assigned to an administrative role, the compliance application may classify the digital application as non-compliant.

[0008] In yet another example approach, the compliance application may utilize security monitoring and logging APIs to analyze security events and detect anomalies. By integrating with Security Information and Event Management (SIEM) platforms, such as Splunk, Datadog, or AWS CloudTrail, the compliance application may retrieve security logs that detail authentication failures, privilege escalations, and suspicious access attempts. In some cases, the compliance application may apply rule-based security policies to evaluate the security logs against compliance requirements. For example, if an API response contains log data indicating that multiple failed login attempts have occurred within a short time window or that an unauthorized IP address has accessed sensitive data, the compliance application may flag the event as a potential security incident and recommend further investigation.

[0009] However, these approaches do not provide for identifying specific security parameters, such as specific security tools, a content system has enabled, nor do they provide a content system detailed security information regarding a second content system’s security parameters.

[0010] To help address these problems, systems, methods and apparatuses are disclosed herein for verifying the security specifications of content systems prior to exchanging data. In some embodiments, a security verification system receives an indication of anticipated data exchange between a first content system and a second content system. Based on receiving the indication, the security verification system retrieves a first security profile associated with the first content system and a second security profile associated with the second content system. The first security profile includes security requirements associated with the first content system and the second security profile includes security specifications associated with the second content system. The security verification system determines, based on the first security profile and the second security profile, whether the security specifications associated with the second content system meet the security requirements associated with the first content system. In the event that the security specifications meet the security requirements, a security approval indicationis sent to the first content system. In the event that the security specifications do not meet the security requirements, a security denial indication is sent to the first content system. In this way, the first content system is informed of whether the second content system meets its security requirements before any sensitive data is exchanged.

[0011] In some embodiments, based on receiving the indication of anticipated data exchange, the security verification system sends a verification request to the second content system. The second content system sends a response to the verification request. The determination of whether the security specifications associated with the second content system meet the security requirements associated with the first content system may be further based on the response to the verification request. In some embodiments, the verification request is an application programming interface (API) request and the response to the verification request is an API response. In this way, the security verification system can programmatically retrieve security data from the second content system without requiring manual intervention or disrupting the operations of the second content system.

[0012] In some embodiments, the first security profile includes historical instances of data exchanges between the first content system and a third content system. The determination of whether the security specifications associated with the second content system meet the security requirements associated with the first content system may be further based on those historical instances. In this way, the security verification system can leverage prior data exchange history to inform its verification of the second content system, even when the first content system and the second content system have not previously exchanged data. In some embodiments, a third security profile associated with the third content system is retrieved. Prior to sending the verification request to the second content system, the verification request may be modified based on the third security profile. For example, if the third content system implements a particular security application that the first content system previously accepted as meeting its requirements, the verification request may be modified to account for the particular security application as an acceptable alternative when evaluating the second content system.

[0013] In some embodiments, the first security profile includes historical instances of data exchanges between the second content system and a third content system. The determination of whether the security specifications associated with the second content system meet the security requirements associated with the first content system may be further based on those historical instances. In this way, the security verification system can leverage data exchange history between the second content system and other content systems to inform its verification,even in the absence of direct interaction between the security verification system and the second content system.

[0014] In some embodiments, information related to the first security profile, the second security profile, the security approval indication or the security denial indication is displayed at a user interface accessible by the first content system, the second content system or the security verification system. In this way, users or administrators associated with any of the relevant systems may review the results of the verification and take appropriate action.

[0015] In some embodiments, based on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, the security verification system identifies a security requirement of the first security profile that is not implemented at the second content system. An instruction to implement the identified security requirement is sent to the second content system. In this way, the security verification system not only identifies the deficiency but also provides the second content system with actionable guidance to remediate the deficiency and meet the security requirements of the first content system.

[0016] In some embodiments, based on the indication of anticipated data exchange, the security verification system determines a type of data that is anticipated to be exchanged between the first content system and the second content system. Based on the determined type of data, the security requirements associated with the first content system may be updated. A recommendation to update the security specifications associated with the second content system is sent from the security verification system. In this way, the security requirements are not static but may be dynamically adjusted based on the sensitivity or type of data to be exchanged, and the second content system is notified of the updated requirements so that it may take appropriate measures prior to the data exchange.

[0017] In some embodiments, the second content system is a content system of a plurality of content systems, each having respective security profiles. The security verification system determines, for each of the plurality of content systems, a respective security level. The security verification system also determines, based on the first security profile, a threshold security level. The respective security levels of each of the plurality of content systems are compared to the determined threshold security level. In the event that the security level of any one of the plurality of content systems does not meet the determined threshold security level, a security denial indication is sent to the first content system. In this way, the security verification system ensures that all content systems with which the first content system anticipates exchanging data meet a minimum security threshold, rather than evaluating each content system in isolation.

[0018] In some embodiments, the security verification system includes an agentic system that deploys a plurality of agents to perform verification tasks. The agents may be configured to autonomously query one or more content systems to retrieve security data related to specific security parameters. In some embodiments, the agents communicate with the content systems using application programming interfaces (APIs), command-line interfaces (CLIs), agent-to-agent (A2A) protocols or any other suitable communication protocol or interface. In some embodiments, the agents may be embodied by software agents, rule-based agents, script-based agents, bot agents, polling agents, event-driven agents, proxy agents, orchestration agents, artificial intelligence (Al) agents, machine learning agents or any combination thereof. In this way, the security verification system can deploy multiple agents concurrently to retrieve and verify security data across multiple content systems and multiple security parameters, reducing the time required to perform a comprehensive security verification.

[0019] In some embodiments, the content systems being queried by the agentic system each include their own respective agents. In such embodiments, agents at the agentic system may communicate directly with agents at the content systems using agent-to-agent protocols. The agents at the content systems receive queries, retrieve the requested security data from the content system at which they are implemented and send responses directly to the querying agent. In some embodiments, the agents at the content systems may proactively send security data to the agentic system without waiting for a query, for example, upon detecting a change in a security parameter. In other embodiments, agents at one content system may communicate directly with agents at another content system, independent of the agentic system, and report the results of such communication to the agentic system. In this way, the security verification system supports multiple agent-to-agent communication patterns that enable flexible, distributed and autonomous security verification across content systems.

[0020] In some embodiments, the agentic system compares findings between agents for increased fidelity. For example, the agentic system may compare security data retrieved from a first content system by one set of agents to security data retrieved from a second content system by another set of agents to determine whether the data is consistent. The findings are passed to a processing system that compares the findings to a given security standard or framework and assigns a score based on how well the content systems conform to the given standard. The score is recorded to a corresponding entry in a database. In this way, the security verification system provides an automated, agent-based approach to security verification that leverages autonomous agents to concurrently query and verify security specifications acrossmultiple content systems and security categories, compare findings for accuracy and update security scores based on the verification results.of the

[0021] The present disclosure, in accordance with one or more various embodiments, is described in detail with reference to the following figures. The drawings are provided for purposes of illustration only and merely depict typical or example embodiments. These drawings are provided to facilitate an understanding of the concepts disclosed herein and should not be considered limiting of the breadth, scope, or applicability of these concepts. It should be noted that for clarity and ease of illustration these drawings are not necessarily made to scale.

[0022] The embodiments herein may be better understood by referring to the following description in conjunction with the accompanying drawings in which like reference numerals indicate identically or functionally similar elements, of which:

[0023] FIG. 1 depicts an illustrative diagram for security verification systems, according to various embodiments of the present disclosure;

[0024] FIG. 2 depicts an illustrative flow chart of a process for security verification, according to various embodiments of the present disclosure;

[0025] FIG. 3 depicts an illustrative flow chart of a process for security verification, according to various embodiments of the present disclosure;

[0026] FIG. 4 depicts an illustrative diagram for security verification systems, according to various embodiments of the present disclosure;

[0027] FIG. 5 depicts an illustrative diagram for security verification systems, according to various embodiments of the present disclosure;

[0028] FIG. 6 depicts an illustrative diagram for security verification systems, according to various embodiments of the present disclosure;

[0029] FIG. 7 depicts an illustrative diagram for security verification systems, according to various embodiments of the present disclosure;

[0030] FIG. 8 depicts an illustrative diagram for security verification systems, according to various embodiments of the present disclosure;

[0031] FIG. 9 depicts an illustrative diagram for security verification systems, according to various embodiments of the present disclosure;

[0032] FIG. 10 depicts an illustrative diagram for agent-based security verification systems, according to various embodiments of the present disclosure;

[0033] FIG. 11 depicts an illustrative user interface of a system for security verification, according to various embodiments of the present disclosure;

[0034] FIG. 12 depicts an illustrative user interface of a system for security verification, according to various embodiments of the present disclosure; and

[0035] FIG. 13 depicts an illustrative user interface of a system for security verification, according to various embodiments of the present disclosure.

[0036] The drawings are intended to depict only typical aspects of the subject matter disclosed herein and therefore should not be considered as limiting the scope of the disclosure. Those skilled in the art will understand that the structures, systems, devices, and methods specifically described herein and illustrated in the accompanying drawings are non-limiting exemplary embodiments and that the scope of the present invention is defined solely by the claims.Detailed

[0037] FIG. 1 depicts an illustrative network architecture diagram of a security verification system 100, according to various embodiments of the present disclosure. In example embodiments, data is anticipated to be transferred between first content system 110 and second content system 120 using communications network 150. In such embodiments, the data to be exchanged between first content system 110 and second content system 120 is sensitive. However, before such sensitive data can be transferred between first content system 110 and second content system 120, whether the security specifications implemented at second content system 120 meet the security requirements of first content system 110 must be verified.

[0038] In some embodiments, to verify the security specifications of second content system 120, first content system 110 may send an indication to security verification system 105 via communications network 150 that indicates first content system 110 anticipates exchanging data with second content system 120. First content system 110 may require that second content system 120 verify the security parameters implemented at second content system 120 before the data is to be exchanged.

[0039] In an embodiment, first content system 110 sends a notification to security verification system 105 that indicates first content system 110 will be exchanging data with second content system 120. Based on receiving the notification, security verification system 105 retrieves the security requirements of first content system 110. In some embodiments, the security requirements of first content system 110 may be included with the notification sent to security verification system 105. In other embodiments, security verification system 105 retrieves the security requirements of first content system 110 from a memory or storage device that is localto security verification system 105. Alternatively, security verification system 105 retrieves the security requirements of first content system 110 from a memory or storage device that is remote from security verification system 105 via, e.g., communication network 150. In some embodiments, the security requirements of first content system 110 are included in a security profile associated with first content system 110.

[0040] Security verification system 105 obtains the security specifications implemented at second content system 120. In some embodiments, security verification system 105 sends a request to second content system 120 requesting the security specifications implemented at second content system 120. In some embodiments, the security specifications of second content system 120 may be included with the notification sent to security verification system 105. In other embodiments, security verification system 105 retrieves the security specifications of second content system 120 from a memory or storage device that is local to security verification system 105. Alternatively, security verification system 105 retrieves the security specifications of second content system 120 from a memory or storage device that is remote from security verification system 105 via, e.g., communication network 150. In some embodiments, the security requirements of first content system 110 are included a security profile associated with first content system 110.

[0041] Security verification system 105 verifies that the security specifications implemented at second content system 120 meet the security requirements of first content system 110. In some embodiments, security verification system 105 compares the security requirements of first content system 110 to the security specifications of second content system 120. For example, first content system 110 requires some level of password protection. In such an example embodiment, the security requirements of first content system 110 indicate that first content system 110 requires password protection. Security verification system 105 analyzes the security specifications of second content system 120 to determine whether second content system 120 implements password protection. In the event that second content system 120 implements password protection, security verification system 105 determines that the password requirement of first content system 110 is met.

[0042] In another example, first content system 110 requires a specific type of password protection. In such an example embodiment, the security requirements of first content system 110 indicate that first content system 110 requires a particular type of password protection, for example, multifactor authentication. Security verification system 105 analyzes the security specifications of second content system 120 to determine whether second content system 120 implements multifactor authentication as part of its password protection. In the event thatsecond content system 120 implements multifactor authentication for passwords, verification system 105 determines that the password requirement of first content system 110 is met. Alternatively, in the event that second content system 120 does not implement multifactor authentication for passwords, security verification system 105 determines that the password requirement of first content system 110 is not met.

[0043] In another example, first content system 110 requires a specific application of password protection. In such an example embodiment, the security requirements of first content system 110 indicate that first content system 110 requires a particular application / vendor for managing its passwords, for example, Pazzwerd Protector 3000. Security verification system 105 analyzes the security specifications of second content system 120 to determine whether second content system 120 implements Pazzwerd Protector 3000. In the event that second content system 120 implements Pazzwerd Protector 3000, security verification system 105 determines that the password requirement of first content system 110 is met. In the event that second content system 120 does not implement Pazzwerd Protector 3000, verification system 105 determines that the password requirement of first content system 110 is not met.

[0044] In another example, first content system 110 requires a specific application of password protection or a functional equivalent. In such an example embodiment, the security requirements of first content system 110 indicate that first content system 110 requires a particular application / vendor for managing its passwords, for example, Pazzwerd Protector 3000, or another that provides the same protections. Security verification system 105 analyzes the security specifications of second content system 120 to determine whether second content system 120 implements Pazzwerd Protector 3000. Security verification system 105 determines that although second content system 120 does not implement Pazzwerd Protector 3000, it implements another password protection application, PassWord Keeper. In some embodiments, security verification system 105 analyzes the security requirements of first content system 110 to determine whether PassWord Keeper meets the relevant requirements. Alternatively, security verification system 105 analyzes the security capabilities of Pazzwerd Protector 3000 to determine whether PassWord Keeper includes the same security capabilities. In the event that the relevant security capabilities of PassWord Keeper are functionally equivalent to Pazzwerd Protector 3000, verification system 105 determines that the password requirement of first content system 110 is met. In the event that the relevant security capabilities of PassWord Keeper are not functionally equivalent to Pazzwerd Protector 3000, verification system 105 determines that the password requirement of first content system 110 is not met.

[0045] In the event that security verification system 105 determines that any or all of the security requirements of first content system 110 are not met, security verification system 105 may send, via, e.g., communications network 150, a verification notification to first content system 110 indicating such. In the event that security verification system 105 determines that any or all of the security requirements of first content system 110 are met, security verification system 105 may send, via, e.g., communications network 150, a verification notification to first content system 110 indicating such. In some embodiments, the notification includes only that the requirements are met or not met. In such embodiments, security verification system 105 may prevent first content system 110 from exposure to any information related to second content system 120 other than its security specifications meeting or not meeting the requirements of first content system 110.

[0046] In other example embodiments, the verification notification sent from security verification system 105 to first content system 110 is qualitative. In such example embodiments, the verification notification may include information indicating which specific security requirements of first content system 110 are met or not met. Security verification system 105 may provide, e.g., a side-by-side comparison detailing which requirements are met and those that are not met. In some embodiments, security verification system 105 may additionally provide recommendations as to which security measures may be implemented at second content system 120 to meet the requirements of first content system 110. In such example embodiments, the recommendations may include adding additional security applications or implementing additional features to existing security applications.

[0047] In some embodiments where the security requirements of first content system 110 are met, security verification system 105 effectuates the data exchange between first content system 110 and second content system 120. In some embodiments, the data passes though security verification system 105. In other embodiments, data is exchanged directly between first content system 110 and second content system 120 using, e.g., communications network 150. In yet other embodiments, security verification system 105 may effectuate the transfer of data between first content system 110 and second content system 120 by, for example, causing a network communications link, e.g., a virtual private network, between first content system 110 and second content system 120 through which the data can be transferred. In such embodiments, the communications link can be persistent, e.g., existing for as long as data is exchanged between first content system 110 and second content system 120. In other embodiments, the communications link can be temporary, e.g., existing for a set period of time, e.g., one hour or one day, or existing for a certain amount of data, e.g., a certain number ofpackets, a certain number of bytes of data, or any other data measurement to effectuate the various embodiments discussed herein.

[0048] In some embodiments where the security specifications of second content system 120 do not meet the security requirements of first content system 110, first content system 110 may exchange the data with security verification system 105 that implements the security specifications required by first content system 110 and store that data until second content system 120 meets the security requirements of first content system 110.

[0049] In some embodiments, first content system 110 sends a notification of anticipated data exchange to second content system 120. In such example embodiments, first content system 110 includes a security profile that may include the security requirements of first content system 110. The security requirements may indicate that the security specifications implemented at second content system 120 be verified by, e.g., security verification system 105. In such example embodiments, second content system 120 may send a request for security verification to security verification system 105. Based on receiving the security verification request from second content system 120, security verification system 105 may retrieve security profiles for first content system 110 and second content system 120 and verifies that the security specifications of second content system 120 meet the security requirements of first content system 110 using, e.g., the techniques described herein. Once verified (as either meeting the requirements or not meeting the requirements), security verification system 105 may send a notification to second content system 120 and / or first content system 110 indicting the results of the verification. Such notification may include a token or other information that is authenticable as genuine and / originating from security verification system 105.

[0050] In such embodiments, security verification system 105 may send the request for verification of the security parameters of second content system 120 via, e.g., communications network 150. First content system 110 may receive via, e.g., communications network 150, a verification that the security parameters of second content system 120 meet the security requirements of first content system 110 from security verification system 105.

[0051] In some embodiments, security verification system 105 may query second content system 120 for security data related to a security parameter using, e.g., an API associated with the security parameter. For example, security verification system 105 may use a Pazzwerd Protector 3000 API to retrieve Pazzwerd Protector 3000 security data for second content system 120. In such an example, first content system 110 may send a verification request to security verification system 105. Security verification system 105 generates and sends, e.g., an API that is received at second content system 120, which, in turn, generates and send a response to firstcontent system 110 that indicates Pazzwerd Protector 3000 is implemented and enabled at second content system 120. In this way, first content system 110 verifies that a required security parameters is implemented at second content system 120 before first content system 110 sends any information to second content system. Although certain types or functionalities of APIs may be illustrated and described, any type of API may be implemented without departing from the contemplated embodiments. For example, Simple Object Access Protocol (SOAP) APIs, Remote Procedure Calls (RPC) APIs, Websocket APIs, or Representational State Transfer (REST) APIs, or any combination thereof, may be implemented according to the various contemplated embodiments. Moreover, any of the APIs discussed herein may be implemented as private APIs, public APIs, partner APIs, or composite APIs without departing from the contemplated embodiments. As used herein, security data may refer to any information, metadata, configuration settings, logs, status indicators, policy records, compliance evidence, access control records, authentication data, encryption states, software version information, threat intelligence, vulnerability assessments, can results, audit trails, or any other data relevant to evaluating, verifying, or maintaining the security posture of a device, system, software component, or network.

[0052] FIG. 2 illustrates an exemplary flow diagram in accordance with the features of the present disclosure. At 205, system 200 initializes. In some embodiments, system 200 is initialized when a security verification system (e.g., security verification system 105) receives an indication that a first content system (e.g., first content system 110 as discussed with respect to FIG. 1) anticipates exchanging data with a second content system (e.g., second content system 120 as discussed with respect to FIG. 1). In such embodiments, system 200 is initialized when the indication is received. In other embodiments, system 200 initializes when a first content system implements a security verification system at, e.g., one or more network terminals.

[0053] At 210, the security verification system receives an indication from, e.g., a first content system that indicates an anticipated data exchange with, e.g., a second content system. In such embodiments, the indication may include the identity or other relevant information related to the second content system. In some embodiments, the indication may further include the type of data that is anticipated to be exchanged with the second content system, a level of security required for the anticipated data exchange, and / or the relevant security measures required by the first content system. Additionally, such request may include information related to the relevant security features, protocols, or frameworks required by first content system. For example, the first content system may require the second content system to adhere to a securityframework / standard, for example, CMMC, NIST, NIST CSF, NIST SP, HITRUST CSF, ISO / IEC 27001, FISMA, CIS Controls, SOC2, GDPR, PCI DSS, FFIEC, HIPAA, MITRE ATT&CK, Microsoft SSPA, SOX ITGC, or OSCF.

[0054] At 215, the security verification system retrieves security profiles for the first content system and / or the second content system. In some embodiments, the security profile includes security requirements of either the first content system and / or the security parameters of second content system. For example, the security profile for the first content system may specify a type of security measure that must be implemented by the second content system before exchanging data. In such an example, the first content system security profile may specify that the second content system must use some level of password protection before data can be exchanged. In another example, the security profile of the first content system may specify that the second content system must use multi-factor authentication before data can be exchanged. In yet another example, the security profile of the first content system must specify a specific type (i.e., a specific product) of password protection, e.g., Pazzwerd Protector 3000, before data can be exchanged between the first content system and the second content system. In this way, the security verification system ensures that the requirements of the first content system are satisfied before data is exchanged between the first content system and the second content system.

[0055] In some embodiments, the security profile of the first content system and / or the security profile of the second content system may be stored at the security verification system, the first content system, the second content system, or at a remote location. In an example embodiment where the profiles are stored at the security verification system, the security verification system may retrieve the local information related to the profiles of either the first content system or the second content system.

[0056] In an example embodiment where security profiles are stored at the first content system, the first content system may send the security profile of the first content system and / or the security profile of the second content system to the security verification system. In some embodiments, the security profiles of the first content system and second content system may be sent along with the request, as described with respect to 210.

[0057] In yet another embodiment, the security profile of the second content system may be stored at the second content system. In such embodiments, the security verification system may, in response to receiving the request as described with respect to 210, send a request to the second content system for the security profile. The second content system may respond by providing its security profile to the security verification system. The security profile of thesecond content system may include the security measures implemented at the second content system. Alternatively, the security profile of second content system may include the security framework implemented at the first content system and / or second content system.

[0058] In yet another embodiment, the security profile of the first content system and / or the security profile of the second content system may be stored at a remote database. In such embodiments, the security verification system may retrieve the security profiles for the first content system and / or the second content system from the external database.

[0059] At 220, security verification system determines whether the security specifications of the second content system meet the requirements of the first content system. In an embodiment, the security verification system analyzes the security profile of the first content system (e.g., the security profile discussed with respect to 215) to determine the requirements of the second content system. In some embodiments, the requirements of the first content system include specifying certain applications or parameters. For example, the security profile of the first content system specify that a specific application be implemented, e.g., Pazzwerd Protector 3000. In another example, the security profile of the first content system specify that a type of security parameter be implemented, e.g., multi-factor authentication, without specifying a specific application. In another example, the security profile of the first content system specify that a generalized type of security parameter be implemented, e.g., password protection, without specifying a particular application or a particular parameter. Although password protection security parameters may be illustrated and described, the security verification system may analyze any security parameter / feature without departing from the contemplated embodiments.

[0060] In some embodiments, the security verification system may include a client application implemented at the first content system and / or the second content system. In such embodiments, the application collects information related to the security parameters or requirements at the first content system or second content system. Such information collection may be periodic, e.g., every hour, every day, every month, every year, etc., or continuous. Although certain periods may be discussed, the security verification system can implement any periodicity, including asymmetric or irregular, without departing from the contemplated embodiments. Additionally, the periodicity may vary depending on one or more factors. For example, the periodicity may change based on the type of data to be exchanged, the sensitivity of the data to be exchanged, the security requirements of the first content system, the security parameters in place at the second content system, the time or day, geography of the first content system or second content system, or any other factor relevant to the periodicity.

[0061] Implementing a client application is beneficial for several reasons. For example, when determining whether the security specifications of the second content system meet the requirements of the first content system, the security verification system may send and receive information to and from the client application implemented at the first content system and second content system. In such example embodiments, the security verification system can verify the requirements of the first content system and the parameters implemented at the second content system without human interaction or disrupting / interfering with the systems implemented at either the first content system or the second content system. In this way, the security verification system can monitor the security requirements and / or security parameters implemented in real time to effectuate the techniques described herein.

[0062] In the event that the security verification system determines that the security specifications of the second content system meet the requirements of the first content system, process 200 proceeds to 225. In the event that security verification system determines that the security specifications of the second content system do not meet the requirements of the first content system, process 200 proceeds to 235.

[0063] At 225, the security verification system sends a notification to the first content system indicating that the requirements of the first content system are met with respect to the security parameters in place at the second content system. In some embodiments, the security verification system sends a notification to the first content system via, e.g., network 150 as discussed with respect to FIG. 1. In some embodiments, the notification may be qualitative in that it additionally includes the parameters that are in place at the second content system and may, in some embodiments, detail how the requirements of the first content system are met. In other embodiments, the notification is merely binary, e.g., yes or no, and simply indicate that the security specifications of the second content system meet the requirements of the first content system without any further details or information.

[0064] At 230, the security verification system optionally causes the data to be exchanged between the first content system and the second content system. In some embodiments, the data is transferred from the first content system to the second content system by using the security verification system as a pass through. In such embodiments, the first content system transfers the data to the security verification system which then, in turn, transfers the data to the second content system. At the conclusion of 230, process 200 proceeds to 250, where process 200 exits. In some embodiments, after 250, process 200 returns to 205 where process 200 begins.

[0065] Returning to 220, when the security verification system determines that the specifications of the second content system do not meet the requirements of the first contentsystem, process 200 proceeds to 235. At 235, the security verification system sends a notification to the first content system indicating that the security requirements of the first content system are not met.

[0066] In some embodiments, the notification is qualitative. In such embodiments, the notification details the specific security requirements that are not met, and in some embodiments, the security verification system additionally provides recommendations based on the security requirements that are not met. For example, if the security verification system determines that the second content system does not include a required password protection parameter, the notification may include a recommended password protection parameter and / or a specific application. For example, the notification may include a recommendation to use multi-factor authentication. In another example, the notification may include a recommendation to use, e.g., Pazzwerd Protector 3000.

[0067] In some embodiments, the notification is sent to the first content system. In other embodiments, the notification is sent to the first content system and the second content system. In other embodiments, the notification is merely binary, e.g., yes or no, without any further information.

[0068] The notification discussed with respect to 235 and 225 may be the same regardless of the recipient. For example, first content system and the second content system may receive the same notification. In other embodiments, the notification varies depending on recipient. In such embodiments, the notification that is sent to the first content system may be different than the notification that is sent to the second content system. For example, a notification indicating that the security requirements are not met may be purely binary when sent to the second content system but, for the same anticipated data exchange, the notification that is sent to the first content system is qualitative and includes details or additional information that indicates the basis for the second content system not meeting the security requirements of the first content system, and vice versa.

[0069] At 240, the security verification system may prevent the exchange of data between the first content system and the second content system. In some embodiments, the security verification system may send an instruction to the first content system to abstain from exchanging data with the second content system. In embodiments where the security verification system is utilized as a passthrough for the exchange of data, the security verification system will not send the data to the second content system.

[0070] FIG. 3 illustrates an example process implementing the features and techniques of the present disclosure. At 305, system 300 begins. In some embodiments, system 300 is initializedwhen a security verification system (e.g., security verification system 105) receives an indication that a first content system anticipates exchanging data with a second content system. In such embodiments, system 300 is initialized when the indication is received. In other embodiments, system 300 initializes when a first content system implements a security verification system at, e.g., one or more network terminals.

[0071] At 310, the security verification system receives an indication from, e.g., a first content system, that indicates an anticipated data exchange with, e.g., a second content system. In such embodiments, the indication may include the identity or other relevant information related to the second content system. In some embodiments, the indication may further include the type of data that is anticipated to be exchanged with the second content system, a level of security required for the anticipated data exchange, the relevant security measures required by the first content system, and / or a security framework.

[0072] At 315, the security verification system retrieves security profiles for the first content system and / or the second content system. In some embodiments, the security profile includes security requirements of either the first content system and / or the second content system. For example, the security profile for the first content system may specify a type of security measure that must be implemented by the second content system before exchanging data. In such an example, the security profile of the first content system may specify that the second content system must use some level of password protection before data can be exchanged. In another example, the security profile of the first content system may specify that the second content system must use multi-factor authentication before data can be exchanged. In yet another example, the security profile of the first content system must specify a specific type (i.e., a specific product) of password protection, e.g., Pazzwerd Protector 3000, before data can be exchanged between the first content system and the second content system. In this way, the security verification system ensures that the requirements of the first content system are satisfied before data is exchanged between the first content system and the second content system.

[0073] In some embodiments, the security profile of the first content system and / or the security profile of the second content system may be stored at the security verification system, the first content system, and / or the second content system. In an example embodiment where the profiles are stored at the security verification system, the security verification system may retrieve he profiles of either the first content system or the second content system from local storage.

[0074] In an example embodiment where security profiles are stored at the first content system, the first content system may send the security profile of the first content system and / or the security profile of the second content system to the security verification system. In some embodiments, the security profiles of the first content system and second content system may be sent along with the request, as described with respect to 310.

[0075] In yet another embodiment, the security profile of the second content system may be stored at the second content system. In such embodiments, the security verification system may, in response to receiving the request as described with respect to 310, send a request to the second content system for the security profile of the second content system. The second content system may respond by providing its security profile to the security verification system.

[0076] In yet another embodiment, the security profile is the first content system and / or the security profile of the second content system may be stored at a remote database. In such embodiments, the security verification system may retrieve the security profiles for the first content system and / or the second content system from the external database.

[0077] At 320, the security verification system sends a verification request to the second content system. In some embodiments, the security verification system sends the request in response to receiving the request from the first content system to exchange data with the second content system, as discussed with respect to 310. The verification request sent to the second content system main clue various types of information. For example, the request may include information related to the first content system, e.g., The identity of the first content system, the security requirements of the first content system, the type of data to be exchanged, or any other information relevant to the exchange of data between the 1st and 2nd content systems.

[0078] At 325, the security verification system receives a response from the second content system. In some embodiments, the response merely includes an acknowledgement that the second content system received the verification request (as discussed with respect to 320). In another embodiment, the verification response received from the second content system includes security parameters implemented at the second content system. For example, the verification response may include an indication that the second content system implements multifactor authentication. In other embodiments, the response further includes the specific applications and / or security measures that are implemented at the second content system. For example, the response may include an indication that the second content system implements a specific password protection application, e.g., Pazzwerd Protector 3000. In embodiments where the second content system implements a client application of the security verificationsystem, the client application may receive the verification request from security verification system and respond with relevant information.

[0079] At 330, the security verification system determines whether the security parameters of the second content system meet the requirements of the first content system. In an embodiment, the security verification system analyzes the security profile of the first content system (e.g., the security profile discussed with respect to 315) to determine the requirements of the first content system. In some embodiments, the requirements of the first content system include specifying certain applications or parameters. For example, the security profile of the first content system specifies that a specific application be implemented, e.g., Pazzwerd Protector 3000. In another example, the security profile of the first content system specifies that a type of security parameter be implemented, e.g., multi-factor authentication, without specifying a specific application. In another example, the security profile of the first content system specifies that a generalized type of security parameter be implemented, e.g., password protection, without specifying a particular application or a particular parameter. Although password protection security parameters may be illustrated and described, the security verification system may evaluate and / or analyze any security parameter without departing from the contemplated embodiments.

[0080] In some embodiments, the security verification system may include a client application implemented at the first content system and / or the second content system. In such embodiments, the application collects information related to the security parameters or requirements at the first content system or second content system. The information collection may be periodic, e.g., every hour, every day, every month, every year, etc., or continuous. Although certain periods may be discussed, the security verification system can implement any periodicity, including asymmetric or irregular, without departing from the contemplated embodiments. Additionally, the periodicity may vary depending on one or more factors. For example, the periodicity may change based on the type of data to be exchanged, the sensitivity of the data to be exchanged, the security requirements of the first content system, the security parameters in place at the second content system, or any other factor relevant to the periodicity.

[0081] Implementing a client application at the first content system or the second content system enables certain functionalities. For example, when determining whether the security specifications of the second content system meet the requirements of the first content system, the security verification system may send and receive information to and from the client application implemented at the first content system and second content system. In such example embodiments, the security verification system can verify the requirements of the firstcontent system and the parameters implemented at the second content system without human interaction or disrupting / interfering with the systems implemented at either the first content system or the second content system. In this way, the security verification system can monitor the security requirements and / or security parameters implemented in real time to effectuate the techniques described herein.

[0082] In the event that the security verification system determines that the security specifications of the second content system meet the requirements of the first content system, process 300 proceeds to 335. In the event that security verification system determines that the security specifications of the second content system do not meet the requirements of the first content system, process 300 proceeds to 340.

[0083] At 335, the security verification system sends a notification to the first content system indicating that the requirements of the first content system are met with respect to the security parameters in place at the second content system. In some embodiments, the security verification system sends a notification to the first content system via, e.g., network 150 as discussed with respect to FIG. 1. In some embodiments, the notification may be qualitative and additionally indicates the parameters that are in place at the second content system and may, in some embodiments, detail how the requirements of the first content system are met. In other embodiments, the notification is merely binary, e.g., security requirements are met or not met, and simply indicate that the security specifications of the second content system meet the requirements of the first content system without any further details or information. At the conclusion of 335, process 300 proceeds to 350, where process 300 exits.

[0084] Returning to 330, when the security verification system determines that the security specifications of the second content system do not meet the security requirements of the first content system, process 300 proceeds to 340. At 340, process 300 determines whether there are alternative security specifications that would meet the security requirements of the first content system. In such embodiments, the security verification system analyzes the security specifications of the second content system to determine whether they offer sufficiently similar functionality or protection. For example, the security requirements of the first content system require the second content system to implement Pazzwerd Protector 3000 but, instead, the second content system implements a different password protection asset, Password Keeper. The security verification system may analyze the features and characteristics of Pazzwerd Protector 3000 and PassWord Keeper to determine if the features and / or protections are sufficiently similar to Pazzwerd Protector 3000. The features and techniques implemented by each of the password protection asset may be determined from any source, e.g., from thedevelopers. In the event that the security verification system determines that Password Keeper is sufficiently similar to Pazzwerd Protector 3000, the security verification system returns to 320 where it may generate and send another verification request to the second content system to confirm that the second content system implements PassWord Keeper. In the event that the security verification system determines that the second content system does not have sufficiently similar alternatives to the requirements of the first content system, process 300 proceeds to 345.

[0085] At 345, the security verification system sends a notification to the first content system indicating that the security requirements of the first content system are not met. In some embodiments, the notification is qualitative. In such embodiments, the notification details the specific security requirements that are not met, and in some embodiments, the security verification system additionally provides recommendations based on the security requirements that are not met. For example, if the security verification system determines that the second content system does not include a required password protection parameter, the notification may include a recommended password protection parameter and / or a specific application. For example, the notification may include a recommendation to use multi-factor authentication. In another example, the notification may include a recommendation to use, e.g., Pazzwerd Protector 3000.

[0086] In some embodiments, the notification is sent to the first content system or the second content system. In other embodiments, the notification is sent to the first content system and the second content system. In other embodiments, the notification is merely binary, e.g., yes or no, without any further information.

[0087] The notification discussed with respect to 335 and 345 may be the same regardless of the recipient. For example, first content system and the second content system may receive the same notification. In other embodiments, the notification is different. In such embodiments, the notification that is sent to the first content system may be different than the notification that is sent to the second content system. For example, a notification indicating that the security requirements are not met may be purely binary when sent to the second content system but, for the same anticipated data exchange, the notification that is sent to the first content system is qualitative and includes details or additional information that indicates the basis for the second content system not meeting the security requirements of the first content system. At the conclusion of 345, process 300 proceeds to 350, where the process ends. In some embodiments, after 350, process 300 returns to 305 where process 300 begins or reinitializes.

[0088] FIG. 4 illustrates an example network architecture of system 400 for verifying security specifications, according to various embodiments of the present disclosure. In an embodiment, first content system 410, second content system 420, and third content system 430 may communicate with security verification system 405 using communications network 450. First content system 410, second content system 420, and third content system 430 may also communicate with each other using communications network 450. In some embodiments, security verification system 405 may retrieve an identifier or security profile for each of first content system 410, second content system 420, and / or third content system 430 via communications network 450. The identifier may be used to retrieve corresponding security data from a database of enabled security parameters located at one or more remote servers (not pictured).

[0089] In some embodiments, first content system 410 may send an indication to security verification system 405 via communications network 450 that indicates first content system 410 anticipates exchanging data with third content system 430. In some examples, first content system 410 may anticipate exchanging data with third content system 430 by establishing a communication channel, via communications network 450, which may be based on historical instances of security verification. First content system 410 may use security verification system 405 to authenticate or verify the communication channel or other parameters associated with the anticipated data exchange by, for example, using one or more of the techniques described herein. Once first content system 410 receives a verification that the security specifications of third content system 430 meet the requirements of first content system 410, security verification system 405 may send a notification to first content system 410 and / or third content system 430 indicating that the relevant security requirements are met.

[0090] In some embodiments, security verification system 405 may verify the security specifications of third content system 430 to ensure that they meet the security requirements of first content system 410. For example, security verification system 405 may retain records of historical instances of data being transferred between first content system 410 and third content system 430. In the event that security verification system 405 does not have information related to historical instances of data transfer between first content system 410 and third content system 430, security verification system 405 can utilize other instances of data transfer relating to first content system 410 and / or third content system 430.

[0091] In such an example embodiment, security verification system 405 may have access to information related to historical instances of data transfer involving second content system 420. That information may include historical instances of data transfer between second contentsystem 420 and third content system 430. In such embodiments, security verification system 405 analyzes the historical instances of data transfer between second content system 420 and third content system 430 to determine the security specifications of third content system 430. Based on that analysis, security verification system 405 may determine that the security specifications of third content system 430 meet (or do not meet) the security requirements of first content system 410. In this way, security verification system 405 is able to determine whether the security specifications of third content system 430 meet the security requirements of first content system 410 based on historical instances of data transfer, even though first content system 410 and third content system 430 may have not historically exchanged data. Information related to historical instances of data transfer may be stored at, and retrieved from, security verification system 405, first content system 410, second content system 420, third content system 430, and / or one or more remote storage databases (not pictured).

[0092] In some embodiments, security verification system 405 may query or otherwise communicate with first content system 410, second content system 420, and / or third content system 430 to verify security requirements are met. In an embodiment, second content system 420 may anticipate exchanging data with third content system 430 via communications network 450. Second content system 420 may send an access key (or any other form of authorization token) to security verification system 405 via communications network 450. Security verification system 405 receives the access key from second content system 420 and issues an API request using the access key to third content system 430. For example, security verification system 405 may issue an API request to a security capability discovery service implemented at third content system 430, which responds with security data describing the transmission, authentication mechanisms, and / or access control policies, among other types of security data. In some embodiments, security verification system 405 may also store the security data from the API response in storage at security verification system 405 and periodically or continuously update the security data with the same access key or other information.

[0093] In some embodiments, the security verification system 405 may send the security data to first content system 410. For example, first content system 410 may request security verification of second content system 420. In some embodiments, security verification system 405 may communicate with third content system 430 on behalf of first content system 410 to verify that second content system 420 implements the security parameters of third content system 430. Security verification system 405 may then send the security verification certificate or other form of authentication to first content system 410.

[0094] In some embodiments, security verification system 405 may, after receiving an access key from second content system 420, send the access key to third content system 430, via communications network 450. Third content system 430 may use the access key to retrieve security data corresponding to second content system 420 from an internal database located at third content system 430 or another storage medium remote from third content system 430, e.g., at security verification system 405, first content system 410, and / or second content system 420.

[0095] In some embodiments, third content system 430 may request security data related to first content system 410 and / or second content system 420 from security verification system 405. In an example embodiment, first content system 410 and second content system 420 may be subsidiaries of third content system 430. Third content system 430 may require periodic or continuous updates regarding the security data of first content system 410 and / or second content system 420. Third content system 430 may receive the updates from security verification system 405, via, e.g., communications network 450.

[0096] In other embodiments, security verification system 405 may collect the security data related to first content system 410 and / or second content system 420 into a single data structure, and send information related to the data structure to third content system 430. For example, security verification system 405 may receive a request from third content system 430 for the security data of all subsidiary content systems (e.g., first content system 410, second content system 420, and any other subsidiary content system). Security verification system 405 may collect the results and share them with, e.g., third content system 430. In this way, security verification system 405 retains records of security data and may aggregate and share that data with relevant systems.

[0097] FIG. 5 illustrates an example network architecture of system 500 for verifying security parameters of first content system 510, second content system 520, third content system 530, and fourth content systems 540a-f. In some embodiments, security verification system 505 includes a database of security profiles for first content system 510, second content system 520, third content system 530, and fourth content systems 540a-f. In some embodiments, security verification system 505 may store a list, an array, or any other kind of data structure with information related to security profiles of first content system 510, second content system 520, third content system 530, and / or fourth system 540a-f.

[0098] In some embodiments, security verification system 505 may generate an indication of the types of security specifications that first content system 510, second content system 520, third content system 530, and / or fourth content systems 540a-f have enabled based on a datastructure that includes the security profiles for each content system. For example, security verification system 505 may generate for display on a user equipment device (e.g., a computer, laptop, smartphone, or any other type of device) a dashboard displaying the various security specifications that first content system 510, second content system 520, third content system 530, and / or fourth content systems 540a-f have implemented.

[0099] In some embodiments, security verification system 505 may receive a request from one of first content system 510, second content system 520, third content system 530, and / or fourth content systems 540a-f to verify the security specifications of one or more of the other content systems. For example, first content system 510 may send a request to security verification system 505 to verify the security specifications of second content system 520. In another example, first content system 510 may send a request to security verification system 505 to verify the security specifications of third content system 530. In yet another example, first content system 510 may send a request to security verification system 505 to verify the security specification of one of fourth content systems 540a-f. Security verification system 505 may receive these requests via communications network 550. Communications network 550 is configured to support bilateral communications among first content system 510, second content system 520, and third content system 530. Fourth content systems 540a-f may communicate with first content system 510, second content system 520, and security verification system 505 via third content system 530 and communications network 550.

[0100] Since communications network 550 is configured to support bilateral communications, in some examples, second content system 520 may receive a request to verify the security specification of one of first content system 510, third content system 530, and / or fourth content systems 540a-f. In other examples, third content system 530 request to verify the security specifications of first content system 510, second content system 520, and / or fourth content systems 540a-f. In yet other examples, one of fourth content systems 540a-f may request to verify the security specification of first content system 510, second content system 520, and / or third content system 530.

[0101] In an example where security verification system 505 receives a request from first content system 510 to verify the security specifications of second content system 520, first content system 510 may send the request to verify the security specifications to security verification system 505 while establishing a communications channel between first content system 510 and second content system 520. The established communications channel may be via communications network 550, or via an external communications network that includes first content system 510 and second content system 520. First content system 510 may send arequest to verify security specifications in response to receiving a notification or data set via, e.g., communications network 550. In other embodiments, first content system 510 may send a request to verify security specifications prior to sending a notification or other data to second content system 520 via, e.g., communications network 550. Security verification system 505 may send a query to second content system 520 to identify the security profile / specifications of second content system 520. The query may include requirements of first content system 510 that include specific security parameters that must be enabled before data can be exchanged between content first and second content systems 510, 520. In some examples, the query may be a survey or questionnaire listing the security parameters that are required by first content system 510. Such surveys or questionnaire listings may be analyzed and responded to manually or automatically. In other examples, the query may be an API request to an API implemented at either second content system 520 or a security services provider to retrieve data related to the security specification of second content system 520. In yet other examples, security verification system 505 may retrieve, from a database, security specifications of second content system 520, and the other content systems discussed with respect to FIG. 5. Security verification system 505 verifies whether the security specification of second content system 520 includes the security parameters required by first content system 510.

[0102] For example, the security requirements of first content system 510 may indicate that Pazzwerd Protector 3000 must be implemented in all content systems exchanging data with first content system 510. First content system 510 sends a request to security verification system 505 to verify whether second content system 520, engaging in communications with first content system 510, implements Pazzwerd Protector 3000. Security verification system 505 retrieves data related to the security specifications of second content system 520 and determines whether the security specifications include Pazzwerd Protector 3000. The security specifications of second content system 520 may include other security parameters, e.g., Password Keeper, along with Pazzwerd Protector 3000. Security verification system 505 may verify that second content system 520 enables all security parameters required by first content system 510. In embodiments where second content system 520 does not implement Pazzwerd Protector 3000, security verification system 505 may notify first content system 510 that second content system 520 does not implement all security parameters required by first content system 510. In some embodiments, security verification system 505 may further notify second content system 520 of the specific security parameters that are required prior to exchanging data with first content system 510. In some embodiments, security verification system 505 may automatically install, activate, or otherwise implement the required security specification(s) atsecond content system 520. In other embodiments, security verification system 505 may send instructions to implement the required security specification(s) at second content system 520.

[0103] In another example where security verification system 505 receives a request from first content system 510 to verify the security specifications of third content system 530, first content system 510 may send a request to verify the security specifications to security verification system 505 while establishing a communications channel between first content system 510 and third content system 530. The established communications channel may be via communications network 550, or via an external communications network that includes first content system 510 and third content system 530. First content system 510 may send a request to verify security specification in response to receiving a message via, e.g., communications network 550. In other embodiments, first content system 510 may send a request to security verification system 505 to verify security specifications prior to exchanging data with third content system 530 via communications network 550. Security verification system 505 may send a query to third content system 530 to identify the security specifications of third content system 530. The query may include requirements of first content system 510, received from first content system 510 by security verification system 505, of specific security parameters that must be enabled before data can be exchanged between first content system 510 and third content system 530. In some examples, the query may be a survey or questionnaire listing the security parameters that are required by first content system 510. In other examples, the query may be an API request to an API implemented at either third content system 530 or to a security services provider to retrieve data related to the security specification of third content system 530. For example, security verification system 505 may send an API request to, e.g., the proprietors associated with Pazzwerd Protector 3000 to verify that third content system 530 implements Pazzwerd Protector 3000. Such verification may be effectuated by the proprietors associated with Pazzwerd Protector 3000 confirming that, according to their records, third content system 530 has an open and active license to implement Pazzwerd Protector 3000.

[0104] In yet other examples, security verification system 505 may already have access to the security specification of third content system 530, and other content systems illustrated in FIG.5, e.g., stored in an internal or external database. Security verification system 505 verifies whether the security specification of third content system 530 includes the security parameters required by first content system 510. For example, first content system 510 may require Pazzwerd Protector 3000 to be installed in all content systems engaged in communications with first content system 510. First content system 510 sends a request to security verification system 505 to verify whether third content system 530, engaging in data exchange with firstcontent system 510, implements Pazzwerd Protector 3000. Security verification system 505 retrieves data related to the security specification of third content system 530 and determines whether the security specification includes Pazzwerd Protector 3000. The security specifications of third content system 530 may include other security parameters, e.g., Password Keeper, along with Pazzwerd Protector 3000. Security verification system 505 may verify that third content system 530 enables all the security parameters required by first content system 510. In embodiments where third content system 530 does not have Pazzwerd Protector 3000 implemented, security verification system 505 may notify first content system 510 that third content system 530 does not have all the security parameters required by first content system 510. In some embodiments, security verification system 505 may further notify third content system 530 of the specific security parameters that are needed prior to exchanging data with first content system 510. In some embodiments, security verification system 505 may automatically install the required security parameter at third content system 530. In other embodiments, security verification system 505 may send instructions to implement the security parameter at third content system 530.

[0105] In another example wherein security verification system 505 receives a request from first content system 510 to verify the security specification of one or more of fourth content systems 540a-f, first content system 510 may send a request to verify the security specification to security verification system 505, which may, in some embodiments, occur while establishing a communications channel between first content system 510 and one of fourth content systems 540a-f. The established communications channel may be via communications network 550, or via an external communications network established between first content system 510 and one of fourth content systems 540a-f, e.g., a virtual private network or other communications network. First content system 510 may send a request to verify security specifications in response to receiving a query. In other embodiments, first content system 510 may send a request to verify security specification prior to sending a query to one of fourth content systems 540a-f. Security verification system 505 may send a query to third content system 530 to identify the security specifications of one of fourth content systems 540a-f. The query may include requirements from first content system 510, received by security verification system 505, of specific security parameters that must be enabled prior to exchanging data between first content system 510 and third content system 530. Security verification system 505 may use the techniques described herein to verify whether one of fourth content systems 540a-f implements the security requirements of first content system 510. In some embodiments, security verification system 505 communicates with third content system 530 via communicationsnetwork 550 to retrieve the security profiles of one or more of fourth content systems 540a-f. In such embodiments, third content system 530 and one or more of fourth content systems 540a-f may have previously exchanged data. In such embodiments, third content system 530 may retrieve historical information related to data exchanges including fourth content systems 540a-f. For example, information related to historical data exchanges that involve fourth content system 540a, may be stored at security verification system 505, first content system 510, second content system 520, third content system 530, and / or fourth content system 540b-f.

[0106] FIG. 6 illustrates an example network architecture of system 600 for verifying security parameters of first content system 610 and / or second content system 620 via third content system 630 and fourth content systems 640a-f.

[0107] In an example embodiment, first content system 610 may exchange data with second content system 620. Third content system 630 may be embodied by a security services provider, and fourth content systems 640a-f may be embodied by security services provided by third content system 630. First content system 610 may engage in bilateral communications with second content system 620 by establishing a bidirectional communication protocol that supports both outbound and inbound data exchange, via, e.g., communications network 650. First content system 610 may expose one or more APIs that allow second content system 620 to send communication requests or to receive communication data. First content system 610 may also be configured to consume corresponding APIs or endpoints exposed by second content system 620.

[0108] Security verification system 605 verifies the security parameters of first content system 610 and / or second content system 620 via communications network 650. In one embodiment, security verification system 605 may receive a request to determine and verify the security specifications of second content system 620 from first content system 610 via communications network 650. In another embodiment, security verification system 605 may determine the security parameters of either or both of first content system 610 and second content system 620 continually or periodically during pre-determined or dynamic periods, e.g., once per week, every other data exchange, or every time a certain type of data is exchanged.

[0109] To determine the security parameters of first content system 610 and / or second content system 620, security verification system 605 may retrieve an access key from first content system 610 and / or second content system 620, wherein the access key corresponds to an API of third content system 630. The access key of first content system 610 may be unique and different from the access key of second content system 620. In some embodiments, access keysare created and / or maintained by third content system 630 to create a unique combination of an access key ID and a secret access key. The access key ID serves as a public identifier associated with either first content system 610 or second content system 620, while the secret access key functions as a cryptographic credential used to authenticate API requests. To ensure uniqueness, the key generation may incorporate elements such as cryptographically secure random number generators (CSPRNGs), timestamp entropy, and / organization- or user-specific identifiers. Access key pairs may be stored in a secure credential database with associated metadata at security verification system 605, including the creation time, issuing entity, assigned privileges, expiration timestamp, and last usage activity. Security verification system 605 may enforce policies to prevent reuse or duplication of access keys by validating each newly generated key against existing entries before activation. In some embodiments, access keys are versioned or rotated periodically to reduce the risk of compromise and to maintain compliance with security practices.

[0110] In some embodiments, security verification system 605 retrieves an access key for a specific security capability for first content system 610 or second content system 620 from first content system 610 or second content system 620 via communication network 650. In some embodiments, security verification system 605 sends a request to retrieve the content system’s unique access key for a specific security capability associated with one of content systems 640a-f. Security verification system 605 may send the access key to third content system 630. Third content system 630 may query the API of the one of content systems 640a-f for security data related to first content system 610 or second content system 620 and send the retrieved security data for processing at security verification system 605 via communications network 650.

[0111] In other embodiments, security verification system 605 retrieves an access key for all security capabilities for first content system 610 or second content system 620 from first content system 610 or second content system 620 via communication network 650 by sending a request to retrieve the content system’s unique access key for all security capabilities associated with third content system 630. Security verification system 605 may send the access key to third content system 630. Third content system 630 may query all APIs of all of content systems 640a-f for security data related to first content system 610 or second content system 620, and send the retrieved security data to security verification system 605 via communications network 650.

[0112] FIG. 7 illustrates an example network architecture of system 700 for verifying security parameters of first content system 710, second content system 720, third content system 730, fourth content systems 740a-f, and fifth content system 760.

[0113] In some embodiments, security verification system 705 may receive a request from one of first content system 710, second content system 720, third content system 730, fourth content systems 740a-f, and / or fifth content system 760 to verify the security specification of another content system from first content system 710, second content system 720, third content system 730, fourth content systems 740a-f, and / or fifth content system 760. For example, first content system 710 may send a request to security verification system 705 to verify the security specifications of second content system 720. In another example, first content system 710 may send a request to security verification system 705 to verify the security specifications of third content system 730. In yet another example, first content system 710 may send a request to security verification system 705 to verify the security specifications of one or more of fourth content systems 740a-f. Security verification system 705 may receive these requests via communications network 750.

[0114] Communications network 750 is configured to support bilateral communications among first content system 710, second content system 720, and third content system 730. Fourth content systems 740a-f may communicate with the first content system 710, second content system 720, and security verification system 705 via third content system 730, communications network 750, and / or an external communications network between third content system 730 and fourth content systems 740a-f. Fifth content system 760 may communicate with first content system 710, second content system 720, and security verification system 705 via third content system 730, fourth content systems 740a-f, communications network 750, an external communications network between third content system 730 and fourth content systems 740a-f, and / or an external communications network between fourth content systems 740a-f and fifth content system 760.

[0115] Since communications network 750 is configured to support bilateral communications, in some examples, second content system 720 may send a request to verify the security specifications of any one or more of first content system 710, third content system 730, fourth content systems 740a-f, and / or fifth content system 760. In other examples, third content system 730 may send a request to verify the security specifications of first content system 710, second content system 720, fourth content systems 740a-f, and / or fifth content system 760. In yet other examples, one of fourth content systems 740a-f may send a request to verify the security specifications of first content system 710, second content system 720, third contentsystem 730, and / or fifth content system 760. In other examples, fifth content system 760 may send a request to verify the security specification of first content system 710, second content system 720, third content system 730, and / or fourth content systems 740a-f.

[0116] In an example embodiment, security verification system 705 receives a request from first content system 710 to verify the security specifications of second content system 720. In some embodiments, first content system 710 may send the request to verify the security specifications to security verification system 705 while establishing a communications channel between first content system 710 and second content system 720. The established communications channel may be via communications network 750, or via an external communications network that includes first content system 710 second content and 720. First content system 710 may send a request to verify security specifications in response to receiving a verification request. In other embodiments, first content system 710 may send a request to verify security specifications prior to exchanging data with second content system 720. Security verification system 705 may send a query to second content system 720 to identify the security specifications of second content system 720. The query may include the security requirements of first content system 710 that include the specific security parameters that must be enabled before data can be exchanged between first content system 710 second content and 720. In some embodiments, the query may be a survey or questionnaire listing the security parameters that are required by first content system 710. In other examples, the query may be an API request to an API implemented at either second content system 720 or a security services provider to retrieve data related to the security specifications of second content system 720. In yet other examples, security verification system 705 may already have access to the security specifications of second content system 720, and other content systems illustrated in FIG. 7, for example, stored in a local or remote database.

[0117] Security verification system 705 verifies whether the security specifications of second content system 720 include the security parameters required by first content system 710. For example, first content system 710 may require Pazzwerd Protector 3000 to be installed in all content systems engaged in exchange data with first content system 710. First content system 710 sends a request to security verification system 705 to verify whether second content system 720 implements Pazzwerd Protector 3000. Security verification system 705 retrieves information related to the security specifications of second content system 720 and determines whether the security specifications include Pazzwerd Protector 3000. The security specification of second content system 720 may include other security parameters, e.g., Password Keeper,along with Pazzwerd Protector 3000. Security verification system 705 may verify that second content system 720 implements all security features required by first content system 710.

[0118] In embodiments where second content system 720 does not implement Pazzwerd Protector 3000, security verification system 705 may notify first content system 710 that second content system 720 does implement all security parameters required by first content system 710. In some embodiments, security verification system 705 may further notify second content system 720 of the specific security parameters that are required prior to exchanging data with first content system 710. In some embodiments, security verification system 705 may automatically install the required security parameter in second content system 720. In other embodiments, security verification system 705 may send instructions to implement the security parameter in second content system 720.

[0119] In another example where security verification system 705 receives a request from first content system 710 to verify the security specification of fifth content system 760, first content system 730 may send the request to verify the security specification to security verification system 705. In some embodiments, the request may be sent while a communications channel is established between first content system 710 and fifth content system 760. The established communications channel may be via communications network 750, or via an external communications network between first content system 710 and fifth content system 760. First content system 710 may send a request to verify security specification in response to receiving a from either first content system 710 or fifth content system 760. In other embodiments, first content system 710 may send a request to verify security specification prior to sending a notification to fifth content system 760. Security verification system 705 may send a query to third content system 730 to identify the security specification of fifth content system 760. The query may include the security requirements of first content system 710 that must be implemented before data can be exchanged between first content system 710 and fifth content and 760.

[0120] In some embodiments, security verification system 705 communicates with third content system 730 via communications network 750 to retrieve security specification of fifth content system 760. Third content system 730 and fifth content system 760 may communicate via communications network 750 and / or an external communications network. In such embodiments, third content system 730 may retrieve the security specifications of fifth content system 760 from the one of fourth content systems 740a-f. For example, third content system 730 may have previously exchanged sensitive data with one or more of fourth content systems 740a-f. In those historical instances, third content system would have verified the securityspecifications of fourth content systems 740a-f. Moreover, one or more of fourth content systems 740a-f have also historically exchange sensitive data with fifth content system 760. Before engaging in those historical instances of sensitive data transfer(s), the security specifications of fifth content system 760 would have been verified. Thus, because third content system has previously verified the security specifications of fourth content systems 740a-f, and because fourth content systems 740a-f have also previously verified the security specifications of fifth content system 760, security verification system 705, first content system 710 and / or second content system 720 may request information related to those historical data transfers from third content system 730. With that information, the security specifications of third content system 730, fourth content system 740a-f, and fifth content system 760 may be verified. In some embodiments, security verification system 705 is able to verify the security specifications of, e.g., fifth content system 760 even though security verification system 705 has never directly communicated with fifth content system 760. In this way, the techniques described herein may be used to verify the security specifications of a content system by relying on historical interactions with other content systems. In some embodiments, such historicalbased approach may be dependent on other factors. For example, only certain exchanges may be considered, certain types of data exchanged may be considered, data exchanges from certain periods of time, day, week, year, etc. may be considered, the historical instances may be considered only after a certain threshold is met, or any other factor relevant to verifying security parameters.

[0121] FIG. 8 illustrates an example network architecture of system 800 for verifying security requirements of first content system 810 and second content system 820 based on a request from fifth content system 860 via third content system 830 and fourth content systems 840a-f.

[0122] In an example embodiment, third content system 830 may be embodied by a security services manager (that may also be referred to as a managed security service provider (or MSSP)), and fourth content systems 840a-f may represent individual security service providers. First content system 810 and second content system 820 may be embodied by subsidiaries of fifth content system 860. In such embodiments, first content system 810 and second content system 820 may individually manage their respective security specifications. Fifth content system 860 may require first content system 810 and second content system 820 to change their respective security specifications by, for example, adding a new security feature to their security profiles. Fifth content system 860 may send a request directly to first content system 810 and / or second content system 820 indicating that each implement Pazzwerd Protector 3000. Alternatively, fifth content system 860 may send the notification to securityverification system 805, which, in turn, sends a notification to first content system 810 and second content system 820 indicating the security change.

[0123] In some embodiments, based on receiving the notification from fifth content system 860, first content system 810 and second content system 820 may send a request to security services manager 830. Security services manager 830, in turn, sends a request to security service provider 840a that then communicates with first content system 810 and second content system 820 to cause implementation of Pazzwerd Protector 3000 at first content system 810 and second content system 820. For example, security services manager 830 and / or security service provider 840a cause Pazzwerd Protector 3000 to be downloaded, installed, and configured at first content system 810 and second content system 820. Alternatively, security services manager 830 and / or security service provider 840a may cause Pazzwerd Protector 3000 to be implemented according to other techniques described herein or by any other technique apparent to one skilled in the art. In this way, fifth content system 860 is able to update or otherwise change the security specifications of first content system 810 and second content system 820. Although adding a new security feature may be illustrated and described, any other change to the security specifications of first content system 810 and / or second content system 820 may be implemented without departing from the contemplated embodiments. In some embodiments, security verification system 805 may be embodied by security services manager 830 and vice versa.

[0124] FIG. 9 is an illustrative diagram of depicting network architecture for a system verifying security requirements and specifications 900, according to embodiments of the present disclosure. System 900 includes security verification system 905, first content system 910 and second content system 920, which can communicate using communication network 950. Communication network 950 may include satellite network 980 and cellular network 990. User equipment 930 may be accessed by or implemented at security verification system 905, first content system 910, and / or second content system 920. Security verification system 905, first content system 910, second content system 920, user equipment 930, and / or storage 970 may communicate with each other using communication network 950.

[0125] In example embodiments, data is anticipated to be transferred between first content system 910 and second content system 920 using communications network 950. For example, first content system 910 may send data using input / output (VO) path 912 to transmit data over communication network 950, which is received at second content system 920 using I / O path 922. In such embodiments, the data to be exchanged between first content system 910 and second content system 920 is sensitive. However, before such sensitive data can be exchangedbetween first content system 910 and second content system 920, whether the security specifications implemented at second content system 920 meet the security requirements of first content system 910 must be verified.

[0126] In some embodiments, to verify the security specifications of second content system 920, first content system 910 may send, using I / O path 912, a request to security verification system 905 via communications network 950. First content system 910 may require that second content system 920 verify the security parameters of second content system 920 before any data is exchanged or, alternatively, only when sensitive data is to be exchanged.

[0127] In an embodiment, first content system 910 generates a request using control circuitry 911 and sends it, using I / O path 912, to security verification system 905 over communications network 950 that indicates first content system 910 will be exchanging data with second content system 920. Based on receiving the notification using I / O path 907, security verification system 905 retrieves the security requirements of first content system 910. In some embodiments, the security requirements of first content system 910 may be included with the notification sent to security verification system 905. In other embodiments, security verification system 905 retrieves the security requirements of first content system 910 from a local memory or storage device, e.g., storage 908. Alternatively, security verification system 905 retrieves the security requirements of first content system 910 from a memory or storage device that is remote from security verification system 905, e.g., storage 970, with which it communicates using communication network 950. In some embodiments, the security requirements of first content system 910 are included a security profile associated with first content system 910, which may be stored at storage 908, storage 913, and / or storage 970.

[0128] In some embodiments, storage 970 includes a database of enabled security parameters for each of first content system 910 and second content system 920. For example, storage 970 may include of the types of security parameters that have been implemented at first content system 910 and / or second content system 920. Storage 970 may also include other types of security data related to the content system, such as data related to identity and access management, encryption policies, network security settings, logging confirmations and other information, multi-factor authentication enforcement, storage encryption, account or / and administrative privileges, security profile of first content system 910, security profile of second content system 920, collected security evidence or logs, or any other information or data structure relevant to the techniques described herein.

[0129] Security verification system 905 retrieves the security specifications implemented at second content system 920. In some embodiments, security verification system 905 sends arequest to second content system 920 requesting the security specifications implemented at second content system 920. In such embodiments, second content system 920 may retrieve the security specifications from storage 923 and / or storage 970. In some embodiments, the security specifications of second content system 920 may be included with the notification sent to security verification system 905. In other embodiments, security verification system 905 retrieves the security specifications of second content system 920 from a memory or storage device that is local to security verification system 905, e.g., storage 923. Alternatively, security verification system 905 retrieves the security specifications of second content system 920 from a memory or storage device that is remote from security verification system 905, e.g., storage 970. In some embodiments, the security requirements of first content system 910 are included a security profile associated with first content system 910, which may be stored at storage 908 or storage 970.

[0130] Security verification system 905 verifies that the security specifications of second content system 920 meet the security requirements of first content system 910. In some embodiments, security verification system 905 compares the security requirements of first content system 910 to the security specifications of second content system 920. For example, first content system requires some level of password protection. In such an example embodiment, the security requirements of first content system 910 indicate that first content system 910 requires password protection. Security verification system 905 analyzes the security specifications of second content system 920 to determine whether second content system 920 implements some form of password protection. In the event that second content system 920 implements some form of password protection, verification system 905 determines that the password requirement of first content system 910 is met.

[0131] In the event that security verification system 905 determines that any or all of the security requirements of first content system 910 are not met, security verification system 905 may send, via, e.g., communications network 950, a notification to first content system 910 indicating such. In the event that security verification system 905 determines that any or all of the security requirements of first content system 910 are met, security verification system 905 may send, via, e.g., communications network 950, a notification to first content system 910 indicating such. In some embodiments, the notification includes only that the requirements are met or not met. In such embodiments, security verification system 905 prevents first content system 910 from exposure to any information related to second content system 920 other than its security specifications meeting or not meeting the requirements of first content system 910.

[0132] In other example embodiments, the notification sent from security verification system 905 to first content system 910 is qualitative. In such example embodiments, the notification may include information indicating which specific security requirements of first content system 910 are met or not met. Security verification system 905 may provide, e.g., a side-by-side comparison detailing which requirements are met and those that are not met. In some embodiments, security verification system 905 may additionally provide recommendations as to which security measures may be implemented at second content system 920 to meet the requirements of first content system 910. In such example embodiments, the recommendations may include adding additional security applications or implementing additional features to existing security applications.

[0133] In some embodiments where the security requirements of first content system 910 are met, security verification system 905 effectuates the data exchange between first content system 910 and second content system 920. In some embodiments, the data passes though security verification system 905. In other embodiments, data is exchanged directly between first content system 910 and second content system 920 using, e.g., communications network 950. In yet other embodiments, security verification system 905 may effectuate the transfer of data between first content system 910 and second content system 920 by, for example, causing a network communications link, e.g., a virtual private network, between first content system 910 and second content system 920 through which the data can be transferred. In such embodiments, the communications link can be persistent, e.g., existing for as long as data is exchanged between first content system 910 and second content system 920. In other embodiments, the communications link can be temporary, e.g., existing for a set period of time, e.g., one hour or one day, or existing for a certain amount of data, e.g., a certain number of packets, a certain number of bytes of data, or any other data measurement.

[0134] In some embodiments where the security specifications of second content system 920 do not meet the security requirements of first content system 910, first content system 910 may exchange the data with security verification system 905 that implements the security specifications required by first content system and store that data until second content system meets the security requirements of first content system.

[0135] In some embodiments, the results or other information relevant to the security verification may be displayed at user equipment 930. User equipment may be embodied by any device suitable for displaying information and / or receiving user input, for example, a cellular telephone, a tablet, a laptop computer, a computer, a smartwatch (or other wearable technological device), or other electronic device. User equipment 930 may be configured todisplay information and / or to receive user input. For example, a user or administrator associated with security verification system 905, first content system 910, and / or second content system 920 may access and use user equipment 930. In some embodiments, security verification system 905, first content system 910, and / or second content system 920 may each include a user equipment device 930. For example, in some embodiments where security verification system 905 has administrative capabilities related to the security specifications at, e.g., second content system 920, user equipment 930 accessible at security verification system 905 may receive user input to engage, disengage, change, or otherwise alter the security specifications implemented at second content system 920. In this way, security verification system 905 (or a user / system administrator associated therewith) may change the security specifications at second content system 920 to meet the security requirements of first content system 910.

[0136] FIG. 10 depicts an illustrative diagram of an on-demand, agentic, and autonomous security verification system 1000, according to various embodiments of the present disclosure. System 1000 includes database 1010, processing system 1020, agentic system 1030, first content system 1040 and second content system 1050. In some embodiments, system 1000 optionally includes third content system 1060, which, in some embodiments, optionally includes agents 1065a-n. In some embodiments, database 1010 may be embodied by a relational database, a non-relational database, a data warehouse or any other storage system configured to store security profiles, security scores, and verification histories associated with one or more content systems. Database 1010 may additionally be embodied by one or more databases that may be local to or remote from each other. In some embodiments, processing system 1020 may be embodied by a security scoring engine, a compliance scoring platform, a risk assessment system or any other system configured to generate, update and maintain security scores based on verification results. In some embodiments, agentic system 1030 may be embodied by a multi-agent platform, an agent orchestration framework, a distributed task execution system or any other system configured to deploy and coordinate a plurality of agents to perform security verification tasks. In some embodiments, first content system 1040 may be embodied by a user device management system, such as a mobile device management (MDM) system, a unified endpoint management (UEM) system, a device enrollment platform or any other system configured to register, manage and monitor endpoints. As used herein, “endpoint” refers to any device, system, database or data lake, or software component that connects to, communicates with, or is managed by a content system via a communications network.

[0137] In some embodiments, second content system 1050 may be embodied by a user security application system, such as an endpoint detection and response (EDR) system, an antivirus system, an endpoint protection platform (EPP) or any other security system configured to monitor, detect and respond to threats at endpoints. In some embodiments, first content system 1040 includes agents 1045a-n configured to receive queries from agentic system 1030, retrieve the requested security data from first content system 1040 and provide responses to agentic system 1030. In some embodiments, second content system 1050 includes agents 1055a-n configured to receive queries from agentic system 1030, retrieve the requested security data from second content system 1050 and provide responses to agentic system 1030. In some embodiments, agentic system 1030 may correspond to, or be implemented as part of, security verification system 105 as discussed with respect to FIG. 1. First content system 1040 and second content system 1050 may correspond to first content system 110 and second content system 120, respectively, as discussed with respect to FIG. 1.

[0138] In some embodiments, agentic system 1030 includes agents 1030a-n and agents 1035a-n. Each of agents 1030a-n and 1035a-n may be configured to autonomously query one or more content systems to retrieve security data related to specific security parameters. In such embodiments, agents 1030a-n and 1035a-n may communicate with first content system 1040 and / or second content system 1050 using application programming interfaces (APIs), command-line interfaces (CLIs), agent-to-agent (A2A) protocols or any other suitable communication protocol or interface. In embodiments where first content system 1040 includes agents 1045a-n, agents 1030a-n may communicate directly with agents 1045a-n using A2A protocols. In such embodiments, agents 1045a-n receive queries from agents 1030a-n, retrieve the requested security data from first content system 1040 and send responses directly to the querying agent. In embodiments where second content system 1050 includes agents 1055a-n, agents 1035a-n may communicate directly with agents 1055a-n using A2A protocols. In such embodiments, agents 1055a-n receive queries from agents 1035a-n, retrieve the requested security data from second content system 1050 and send responses directly to the querying agent. In some embodiments, each of agents 1030a-n and 1035a-n is assigned a specific verification task or query and operates concurrently with other agents within agentic system 1030. In some embodiments, one or more of agents 1030a-n, 1035a-n, 1045a-n and 1055a-n may be embodied by software agents, rule-based agents, script-based agents, bot agents (e.g., robotic process automation (RPA) bots), polling agents, event-driven agents, proxy agents, orchestration agents, artificial intelligence (Al) agents, machine learning agents, autonomous systems (including self-guided autonomous systems), or any combination thereof. Although aspecific number of agents may be illustrated and described, any number of agents may be implemented within agentic system 1030, first content system 1040 and / or second content system 1050 without departing from the contemplated embodiments.

[0139] In an embodiment, agents 1030a-n are configured to query first content system 1040 to retrieve security data related to a first set of security parameters. For example, a query may be sent by agent 1030a to first content system 1040 requesting a count of endpoints registered at first content system 1040. In embodiments where first content system 1040 includes agents 1045a-n, agent 1045a at first content system 1040 may receive the query from agent 1030a, retrieve the requested data from first content system 1040 and send a response to agent 1030a indicating the number of registered endpoints. A query may be sent by agent 1030b to first content system 1040 requesting a count of endpoints at which a security application has been installed. In such embodiments, agent 1045b at first content system 1040 may receive the query from agent 1030b, retrieve the requested data and send a response indicating the number of endpoints with the security application installed. In other embodiments, agents 1030a-n query first content system 1040 directly without communicating with agents 1045a-n. In some embodiments, agents 1030a-n send their respective queries concurrently. In other embodiments, agents 1030a-n send their respective queries sequentially.

[0140] In some embodiments, agentic system 1030 compares the data received from agents 1030a-n to determine whether the responses satisfy a predetermined condition. For example, agentic system 1030 may compare the count of registered endpoints received from agent 1030a to the count of endpoints with a security application installed received from agent 1030b to determine whether all registered endpoints have the security application installed. In such an example, if an indication is received from agent 1030a that first content system 1040 has 500 registered endpoints, and an indication is received from agent 1030b that 500 endpoints have the security application installed, agentic system 1030 determines that all registered endpoints have the security application installed. In the event that the counts do not match, agentic system 1030 may determine that the security application deployment is incomplete. In another example, the security requirements of a first content system (e.g., first content system 110 as discussed with respect to FIG. 1) may require that one or more endpoints implement Pazzwerd Protector 3000. In such an example, a query may be sent by agent 1030a to first content system 1040 to determine the total number of registered endpoints, and a query may be sent by agent 1030b to first content system 1040 to determine the number of endpoints at which Pazzwerd Protector 3000 has been installed. The responses are compared and, in the event that the count of endpoints with Pazzwerd Protector 3000 installed matches the count of registered endpoints,agentic system 1030 determines that the Pazzwerd Protector 3000 deployment requirement is satisfied. In the event that the counts do not match, agentic system 1030 may determine that the Pazzwerd Protector 3000 deployment requirement is not satisfied and may, in some embodiments, identify the specific endpoints that do not have Pazzwerd Protector 3000 installed.

[0141] In some embodiments, agents 1035a-n are configured to query second content system 1050 to retrieve security data related to a second set of security parameters. For example, a query may be sent by agent 1035a to second content system 1050 requesting a count of registered endpoints at second content system 1050. In embodiments where second content system 1050 includes agents 1055a-n, agent 1055a at second content system 1050 may receive the query from agent 1035a, retrieve the requested data from second content system 1050 and send a response indicating the number of registered endpoints. A query may be sent by agent 1035b to second content system 1050 requesting whether all registered endpoints are actively checking in with second content system 1050. In such embodiments, agent 1055b at second content system 1050 may receive the query from agent 1035b, retrieve the requested data and send a response indicating whether the registered endpoints are actively reporting. In other embodiments, agents 1035a-n query second content system 1050 directly without communicating with agents 1055a-n. In some embodiments, agents 1035a-n send their respective queries concurrently. In other embodiments, agents 1035a-n send their respective queries sequentially. Agentic system 1030 evaluates the responses received from agents 1035a-n to determine whether the registered endpoints at second content system 1050 are actively checking in. In this way, agentic system 1030 verifies not only that a security application is installed across all registered endpoints (based on the queries to first content system 1040 by agents 1030a-n) but also that the installed security application is operational and actively reporting (based on the queries to second content system 1050 by agents 1035a-n).

[0142] In an example embodiment, a first content system (e.g., first content system 110 as discussed with respect to FIG. 1) may require that all endpoints running Pazzwerd Protector 3000 actively check in with second content system 1050 at a predetermined interval. In such an example, a query may be sent by agent 1035a to second content system 1050 to determine the number of endpoints registered with Pazzwerd Protector 3000, and a query may be sent by agent 1035b to second content system 1050 to determine whether each of those endpoints has checked in within the predetermined interval. The responses are compared and, in the event that all registered endpoints have checked in within the predetermined interval, agentic system 1030 determines that the active reporting requirement is satisfied. In the event that one or moreendpoints have not checked in within the predetermined interval, agentic system 1030 may determine that the active reporting requirement is not satisfied and may, in some embodiments, generate a notification identifying the specific endpoints that have failed to check in.

[0143] In addition to the check-in interval, agents 1035a-n may query second content system 1050 for other endpoint security parameters. For example, a query may be sent to second content system 1050 to determine whether the threat signatures or definition files at each registered endpoint are current, e.g., whether antivirus definitions have been updated within a required timeframe. In some embodiments, a query may be sent to second content system 1050 to determine whether a full or scheduled scan has been completed at each endpoint within a required timeframe. In other embodiments, a query may be sent to second content system 1050 to determine whether each endpoint is operating under a required security policy configuration, including whether real-time protection is enabled and whether firewall rules have been applied. In some embodiments, a query may be sent to second content system 1050 to determine whether the security application running on each endpoint is at a required software version or patch level. In other embodiments, a query may be sent to second content system 1050 to determine whether any endpoint has unresolved threats in quarantine or unacknowledged security alerts. In some embodiments, a query may be sent to second content system 1050 to determine the connection state of each endpoint, including whether the endpoint is online, offline or in a degraded connectivity state. In other embodiments, a query may be sent to second content system 1050 to determine whether storage at each endpoint is encrypted according to policy requirements. In some embodiments, a query may be sent to second content system 1050 to determine whether the operating system at each endpoint has been updated with required security patches. Although certain endpoint security parameters may be illustrated and described, agents 1035a-n may query second content system 1050 for any security parameter relevant to the security requirements of the first content system without departing from the contemplated embodiments.

[0144] In some embodiments, agentic system 1030 aggregates the results from agents 1030a-n and agents 1035a-n to generate a verification result. For example, based on determining that all registered endpoints have a security application installed and that all registered endpoints are actively checking in, a verification result may be generated indicating that the security application deployment is successful. In other embodiments, the verification result may be qualitative, indicating not only whether the deployment is successful but also the specific parameters that were verified and the status of each parameter. For example, the verification result may indicate that all endpoints have Pazzwerd Protector 3000 installed, that all threatdefinitions are current, that all endpoints have completed a scheduled scan within the required timeframe and that no endpoints have unresolved quarantine items. In some embodiments, a negative verification result may be generated, indicating which specific parameters were not satisfied and identifying the specific endpoints that are not in compliance. The verification result is sent to processing system 1020.

[0145] processing system 1020 processes the verification result received from agentic system 1030 and generates a scoring instruction based on the verification result. For example, the scoring instruction may include an instruction to add a predetermined number of points to a security score associated with a particular security category, e.g., a threat protection and security operations score. In some embodiments, the scoring instruction may include an instruction to deduct points from the security score based on a negative verification result, e.g., when one or more endpoints are determined to be non-compliant. In other embodiments, the scoring instruction may adjust the security score based on a weighted evaluation of multiple security categories, such that certain categories contribute more to the overall security score then others. The scoring instruction is sent to database 1010. Based on receiving the scoring instruction, the security score associated with the relevant content system is updated at database 1010. In some embodiments, database 1010 stores security profiles, security scores and verification histories for a plurality of content systems. In some embodiments, the scoring instruction and / or the verification result may additionally be sent to first content system 1040, second content system 1050 or a security verification system (e.g., security verification system 105 as discussed with respect to FIG. 1).

[0146] In some embodiments, processing system 1020 may correspond to security verification system 105, 405, 505, 605, 705, 805 or 905 as discussed with respect to FIGs. 1 and 4-9. In other embodiments, processing system 1020 is a separate system that receives verification results from agentic system 1030 and generates scoring determinations independent of the security verification system. Database 1010 may be stored at a storage device local to processing system 1020, at a remote storage device accessible via, e.g., a communications network (e.g., communications network 150, 450, 550, 650, 750, 850 or 950), or at any other storage medium suitable for the techniques described herein.

[0147] In some embodiments, agents 1030a-n and 1035a-n communicate with first content system 1040 and / or second content system 1050 using API requests (or other interface), as discussed with respect to FIGs. 5-8. For example, a REST API request may be issued to a device management endpoint exposed by first content system 1040. In other embodiments, agents 1030a-n and 1035a-n communicate with first content system 1040 and / or second contentsystem 1050 using CLI commands, A2A protocols or direct system connections. In some embodiments, agents 1030a-n and 1035a-n may communicate with first content system 1040 and / or second content system 1050 using webhook-based communication, message queue or message broker protocols (e.g., MQTT, AMQP or Apache Kafka), remote procedure calls (e.g., gRPC), Simple Network Management Protocol (SNMP), Windows Management Instrumentation (WMI) or Common Information Model (CIM) queries, Secure Shell (SSH) or other remote execution protocols, syslog or other log forwarding protocols, GraphQL or System for Cross-domain Identity Management (SCIM) protocols. Although certain communication protocols and interfaces may be illustrated and described, any communication protocol or interface suitable for retrieving security data from a content system may be implemented without departing from the contemplated embodiments.

[0148] In some embodiments, agents 1045a-n at first content system 1040 and / or agents 1055a-n at second content system 1050 may proactively send security data to agentic system 1030 without waiting for a query from agents 1030a-n or 1035a-n. In such embodiments, agents 1045a-n and / or agents 1055a-n may be configured to monitor the security parameters of the content system at which they are implemented and, upon detecting a change in a security parameter, send a notification to agentic system 1030 indicating the change. For example, agent 1055a at second content system 1050 may detect that a previously active endpoint has stopped checking in and may protractive send a notification to agentic system 1030 indicating the change in connection state. In other embodiments, agents 1045a-n at first content system 1040 may communicate directly with agents 1055a-n at second content system 1050, independent of agentic system 1030, and report the results of such communication to agentic system 1030. For example, agent 1045a at first content system 1040 may query agent 1055a at second content system 1050 to determine whether a newly registered endpoint at first content system 1040 has the required security application installed and actively reporting at second content system 1050. The results of such agent-to-agent communication may be reported to agentic system 1030 for inclusion in the verification result. Although certain agent-to-agent communication patterns may be illustrated and described, any agent-to-agent communication pattern suitable for retrieving, exchanging or reporting security data may be implemented without departing from the contemplated embodiments.

[0149] In some embodiments, agentic system 1030 is configured to perform verification tasks across a plurality of security categories. For example, in addition to verifying security application deployment as described above, agentic system 1030 may deploy additional agents to verify identity and access management parameters, device management and controlparameters and / or cyber threat management parameters, as discussed with respect to FIGs. 10 and 11. In identity and access management embodiments, agents 1030a-n or agents 1035a-n may query a content system or an identity and access management platform, such as Okta, Microsoft Entra ID or Google Workspace, to determine whether multi-factor authentication (MFA) is enforced across all user accounts, whether least privilege access policies are implemented, whether single sign on (SSO) is enabled, whether document control restrictions are in place, whether a specific password protection application (e.g., Pazzwerd Protector 3000 or Password Keeper) has been deployed, whether a privileged user account lacks MFA protection or whether an inactive user account remains assigned to an administrative role. In device management and control embodiments, agents 1030a-n or agents 1035a-n may query a content system or a cloud service provider, such as Amazon Web Services (AWS), Google Cloud Platform (GCP) or Microsoft Azure, to determine whether encryption policies are enforced, whether storage encryption is enabled at each endpoint, whether network security settings conform to a required configuration, whether logging configurations are active or whether infrastructure misconfigurations such as publicly accessible cloud storage buckets are present. In cyber threat management embodiments, agents 1030a-n or agents 1035a-n may query a content system or a Security Information and Event Management (SIEM) platform, such as Splunk, Datadog or AWS CloudTrail, to retrieve security logs that detail authentication failures, privilege escalations, suspicious access attempts or unauthorized IP address access. Based on the query results for each security category, agentic system 1030 may generate a corresponding verification result indicating whether the relevant security requirements of the first content system are satisfied.

[0150] As used herein, the term "user" refers to any entity, whether biological, artificial, automated, or otherwise, that is capable of interacting with, accessing, or utilizing one or more components related to the systems described herein, either directly or indirectly. Nonlimiting examples include, but are not limited to: (i) a human individual directly or indirectly interfacing with the system via input / output mechanisms or any other applicable means; (ii) automated processes, scripts, or software tools initiated, controlled, or utilized by a human; (iii) an artificial intelligence (Al) system operating on behalf of or under the direction of a human; (iv) an agentic Al entity acting autonomously or semi-autonomously on behalf of a human or an authorized Al; and (v) any future interactive systems, technologies, or entities that may be developed or invented subsequent to the filing date hereof, which are capable of similar interactions with the system.

[0151] In some embodiments, the security requirements of the first content system may be defined by a security framework or standard, for example, CMMC, NIST, NIST CSF, NIST SP, HITRUST CSF, ISO / IEC 27001, FISMA, CIS Controls, SOC2, GDPR, PCI DSS, FFIEC, HIPAA, MITRE ATT&CK, Microsoft SSPA, SOX ITGC or OSCF. In such embodiments, agentic system 1030 may deploy agents to verify compliance with the specific controls or requirements defined by the applicable framework. In some embodiments, agentic system 1030 may integrate with third party security tools, such as Amazon Web Services Security Hub, CrowdStrike or lira, to retrieve security data relevant to the verification, processing system 1020 may generate scoring instructions for each verified security category and update the corresponding scores at database 1010.

[0152] In this way, system 1000 provides an automated, agent-based approach to security verification that leverages agents to concurrently query and verify security specifications across multiple content systems and security categories, and to update security scores based on the verification results. Although certain security categories, platforms, frameworks and parameters may be illustrated and described, agentic system 1030 may verify any security parameter, query any platform and evaluate compliance with any framework relevant to the security requirements of the first content system without departing from the contemplated embodiments.

[0153] In an example embodiment of the present disclosure and with reference to FIG 10, agentic system 1030 queries first content system 1040 and second content system 1050 for security data related to the duration settings, security related data, or any other relevant information. For example, agents 1030a-n may query first content system 1040 for password complexity, and / or length requirement settings implemented at first content system 1040. Agents 1035a-n may query second content system 1050 for corresponding password complexity, and / or length requirement settings implemented at first content system 1040. Agents 1035a-n may query second content system 1050 for corresponding password complexity and / or length requirement settings implemented at second content system 1050. In some embodiments, agentic system 1030 compares findings between agents 1030a-n and agents 1035a-n for increased fidelity. For example, agentic system 1030 may compare the password complexity requirements retrieved from first content system 1040 (e.g., by agents 1030a-n) to the password complexity requirements retrieved from second content system 1050 (e.g., by agents 1035a-n) to determine whether the settings are consistent across both first content system 1040 and second content system 1050. In some embodiments, the results are provided to processing system 1020.

[0154] In some embodiments, processing system 1020 compares the findings to a security standard or framework. For example, processing system 1020 may compare the password complexity and / or length requirement settings to the requirements defined by, for example, CIS Controls, NIST, or other applicable framework, as discussed with respect to the various embodiments contemplated herein. Based on the comparison, processing system 1020 may assign a score, indicating how well first content system 1040 and second content system 1050 conform to the standard. Processing system 1020 may then record the generated score(s) to the corresponding entry in database 1010. In some embodiments, the score may be recorded in addition to historical scores, such that the findings in conformity over time may be tracked at, for example, database 1010.

[0155] In another example embodiment of the present disclosure and with reference to FIG 10, first content system 1040 may be embodied by a trusted system that is responsible for, or has control over, the various systems implemented at third content system 1060. in such an example, embodiment, first content system, 1040 maybe embodied by a device management system and third content system 1060 maybe embodied by endpoint systems managed by first content system 10 40. Second content system 10 50 maybe embodied by an enterprise management system associated with the security application, for example, Pazzwerd Protector 3000’s enterprise management system. In such an example embodiment, first content system 1040 may be embodied by, e.g., a device management system, and third content system 1060 may be embodied by, e.g., endpoint systems managed by first content system 1040. Second content system 1050 may be embodied by an enterprise management system associated with a security application, for example, Pazzwerd Protector 3000’s enterprise management system.

[0156] In such embodiments, first content system 1040 is embodied by a trusted system that is responsible for, or has control over, the various systems implemented at third content system 1060. For example, agents 1030a-n may query first content system 1040 for information related to the deployment penetration of Pazzwerd Protector 3000 to endpoint systems implemented at third content system. IN some embodiments, first content system 1040 includes agents 1045a-n that receive the queries from, e.g., agents 1030a-n, retrieve the requested deployment data from first content system 1040 and, in some embodiments, send responses to agents 1030a-n. Agents 1035a-n may query second content system 1050 for the number of deployed Pazzwerd Prorector 3000 licenses. In some embodiments, second content system 1050 includes agents 1055a-n that receive the queries from agents 1035a-n, retrieve the requested license data from second content system 1050, and send responses to agents 1035a-n. In otherembodiments, agentic system 1030 may query third content system 1060 directly via, e.g., agents 1065a-n.

[0157] In such example embodiments, agentic system 1030 compares the findings from first content system 1040 and second content system 1050. For example, agentic system 1030 may compare the number of endpoint systems in third content system 1060 to which Pazzwerd Protector 3000 has been deployed (for example, as reported by first content system 1040) to the number of deployed Pazzwerd Protector 3000 licenses (for example, as reported by second content system 1050). In the event that the deployment count matches the license amount, agentic system 1030 may determine that the Pazzwerd Protector 3000 deployment is complete. In the event that the counts do not match, agentic system 1030 may determine that the deployment is incomplete, e.g., that certain endpoint systems in third content system 1060 do not have Pazzwerd Protector 3000 installed or that unused licenses exist. In some embodiments, the findings are passed to processing system 1020.

[0158] Processing system 1020 compares the findings to the relevant standards, e.g., current NIST standards, or applicable framework. Based on the comparison, processing system 1020 assigns a score and records the score to the corresponding entry in database 1010. In some embodiments, processing system 1020 may additionally identify which specific endpoint(s) systems implemented at third content system 1060 do not conform to the applicable standard and, in some embodiments, may send a notification to first content system 1040, second content system 1050, or security verification system 1005 indicating the non-conforming endpoint system.

[0159] FIG. 11 depicts an illustrative user equipment device 1130, according to various embodiments of the present disclosure. As illustrated, user equipment device 1130 includes a touch screen display with which a user may interact. User equipment device 1130 may be used to review the results of a security verification. As illustrated, user equipment device 1130 indicates that device management and control, and cyber threat management security specifications meet the relevant security requirements. However, the identity and access management security specifications do not meet the security requirements. User equipment device 1130 may be used to further investigate the security verification results, for example, as discussed with respect to FIGs. 12 and 13.

[0160] FIG. 12 depicts an illustrative user equipment device 1230, according to various embodiments of the present disclosure. As illustrated, user equipment device 1230 includes a touch screen display with which a user may interact. User equipment device 1230 may be usedto review the results of a security verification. User equipment device 1230 may display security verification results. As illustrated, the results indicate that identity and access management is determined to be level 1 (e.g., a lower level), device management and control is determined to be level 4 (e.g., a higher level), and cyber threat management is determined to be at level 5 (e.g., the highest level). As compared to user equipment device 1130 as discussed with FIG. 11, user equipment device 1230 displays qualitative security verification results. Although certain numerical levels are illustrated and described, any type of categorization relevant to indicating the security verification results may be used without departing from the contemplated embodiments.

[0161] FIG. 13 depicts an illustrative user equipment device 1330, according to various embodiments of the present disclosure. As illustrated, user equipment device 1330 includes a touch screen display with which a user may interact. User equipment device 1330 may be used to review the results of a security verification and provide user input. User equipment device 1330 may display security verification results. As illustrated, user equipment device 1330 displays certain security specifications relevant to identify and access management. Specifically, multi-factor authentication, Pazzwerd Protector 3000, single sign on (SSO), and document control restrictions.

[0162] In some embodiments, user equipment device 1330 may receive user input to turn on or off multi-factor authentication. In such embodiments, user equipment device 1330 may detect user input associated with multi-factor authentication selectable element 1331. In response to receiving the user input, user equipment device 1330 may send an instruction to a second content system (e.g., second content system 120, 420, 520, 620, 720, 820, 920) to engage or implement multi-factor authentication. In such embodiments, such multi-factor authentication may be required based on the security requirements of a first content system (e.g., first content system 110, 410, 510, 610, 710, 810, 910). Similarly, user equipment device 1130 may detect user input associated with Pazzwerd Protector 3000 selectable element 1132, single sign on (SSO) selectable element 1133, and / or document control restrictions selectable element 1134 to engage or disengage those security specifications at, e.g., the second content system (e.g., second content system 120, 420, 520, 620, 720, 820, 920). In other embodiments, user equipment device 1130 may be used to access and review the security verification results, and / or to engage or disengage security specification or requirements at a first content system (e.g., first content system 110, 410, 510, 610, 710, 810, 910), a second content system (e.g., second content system 120, 420, 520, 620, 720, 820, 920), and / or a security verification system (e.g., security verification system 105, 405, 505, 605, 705, 805, 905). Although certain securityrequirements / specifications are illustrated and described, any security requirement or specification may be accessed, reviewed, engaged, disengaged, or otherwise interacted with using user equipment device 1130, without departing from the contemplated embodiments.

[0163] The computing device 1330 includes control circuitry, a display, and I / O circuitry. The control circuitry can execute systems, methods, processes, and outputs. Both the computing device and server include control circuitry and storage, which can store content, metadata, data, user profiles, messages, and commands for an application. The computing device communicates with an I / O device and can receive and process user inputs locally or transmit them to the remote server for processing. Both the content server and the computing device can transmit and receive content via the communication network or directly, and the processing circuitry receives the user input and converts it to digital signals. The content servers also include control circuitry 752, I / O path 754, and storage 756. Storage 756 may also store access keys for corresponding security parameters.

[0164] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0165] Although at least one exemplary embodiment is described as using a plurality of units to perform the exemplary process, it is understood that the exemplary processes may also be performed by one or plurality of modules. Additionally, it is understood that the term controller / control unit may refer to a hardware device that includes a memory and a processor. The memory may be configured to store the modules, and the processor may be specifically configured to execute said modules to perform one or more processes which are described further below.

[0166] The use of the terms “first”, “second”, “third”, and so on, herein, are provided to identify structures or operations, without describing an order of structures or operations, and, to the extent the structures or operations are used in an exemplary embodiment, the structuresmay be provided or the operations may be executed in a different order from the stated order unless a specific order is definitely specified in the context.

[0167] The methods and / or any instructions for performing any of the embodiments discussed herein may be encoded on computer-readable media. Computer-readable media includes any media capable of storing data. The computer-readable media may be transitory, including, but not limited to, propagating electrical or electromagnetic signals, or may be non-transitory (e.g., a non-transitory computer-readable medium accessible by an application via control or processing circuitry from storage) including, but not limited to, volatile and non-volatile computer memory or storage devices such as a hard disk, floppy disk, USB drive, DVD, CD, media cards, register memory, processor caches, random access memory (RAM), etc.

[0168] The interfaces, processes, and analysis described may, in some embodiments, be performed by an application. The application may be loaded directly onto each device of any of the systems described or may be stored in a remote server or any memory and processing circuitry accessible to each device in the system. The generation of interfaces and analysis there-behind may be performed at a receiving device, a sending device, or some device or processor therebetween.

[0169] The systems and processes discussed above are intended to be illustrative and not limiting. One skilled in the art would appreciate that the actions of the processes discussed herein may be omitted, modified, combined, and / or rearranged, and any additional actions may be performed without departing from the scope of the invention. More generally, the above disclosure is meant to be exemplary and not limiting. Only the claims that follow are meant to set bounds as to what the present disclosure includes. Furthermore, it should be noted that the features and limitations described in any one embodiment may be applied to any other embodiment herein, and flowcharts or examples relating to one embodiment may be combined with any other embodiment in a suitable manner, done in different orders, or done in parallel. In addition, the systems and methods described herein may be performed in real time. It should also be noted that the systems and / or methods described above may be applied to, or used in accordance with, other systems and / or methods.

[0170] This specification discloses various non-limiting embodiments which include, but are not limited to, the following:1. A method comprising:receiving, at a security verification system, an indication of anticipated data exchange between a first content system and a second content system;based on receiving the indication of anticipated data exchange, retrieving a first security profile associated with the first content system and a second security profile associated with the second content system, wherein the first security profile comprises security requirements associated with the first content system, and the second security profile comprises security specifications associated with the second content system;determining, based on the first security profile and the second security profile, whether the security specifications associated with the second content system meet the security requirements associated with the first content system;based on determining that the security specifications associated with the second content system meet the security requirements associated with the first content system, sending, to the first content system, a security approval indication; andbased on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, sending, to the first content system, a security denial indication.2. The method of item 1, further comprising:based on receiving the indication of anticipated data exchange and the second security profile associated with the second content system, sending, from the security verification system, a verification request to the second content system; andreceiving, from the second content system, a response to the verification request;wherein determining whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the response to the verification request.3. The method of item 2, whereinthe verification request comprises an application programming interface (API) request; andthe response to the verification request comprises and API response.4. The method of item 1, whereinthe first security profile includes historical instances of data exchanges between the first content system and a third content system, anddetermining whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the historical instances of data exchanges between the first content system and the third content system.5. The method of item 4, further comprising:retrieving a third security profile associated with the third content system, wherein the third security profile comprises security specifications associated with the third content system; andprior to sending the verification request to the second content system, modifying the verification request based on the third security profile.6. The method of item 1, further comprising:displaying, at a user interface accessible by the first content system, the second content system, or the security verification system, information related to the first security profile, the second security profile, the security approval indication, or the security denial indication.7. The method of item 1, further comprising:based on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, identifying, based on the first security profile, a security requirement of a plurality of security requirements of the first security profile that is not implemented at the second content system; andsending, to the second content system, an instruction to implement the identified security requirement.8. The method of item 1, further comprising:based on the indication of anticipated data exchange between the first content system and the second content system, determining a type of data that is anticipated to be exchanged between the first content system and the second content system;based on the determined type of data:updating the security requirements associated with the first content system; andsending, from the security verification system, a recommendation to update the security specifications associated with the second content system.9. The method of item 1, further comprising:the first security profile includes historical instances of data exchanges between the second content system and a third content system, anddetermining whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the historical instances of data exchanges between the second content system and the third content system.10. The method of item 1, wherein the second content system is a content system of a plurality of content systems, each comprising respective security profiles, the method further comprising:determining, for each of the plurality of content systems, a respective security level;determining, based on the first security profile, a threshold security level; and comparing each of the respective security levels of each of the plurality of content systems to the determined threshold security level;wherein the security denial indication is further based on determining that the security level of any one of the plurality of content systems does not meet the determined threshold security level.11. A system comprising:control circuitry configured to:retrieve, at a security verification system, an indication of anticipated data exchange between a first content system and a second content system;based on receiving the indication of anticipated data exchange, retrieve a first security profile associated with the first content system and a second security profile associated with the second content system, wherein the first security profile comprises security requirements associated with the first content system, and the second security profile comprises security specifications associated with the second content system;determine, based on the first security profile and the second security profile, whether the security specifications associated with the second content system meet the security requirements associated with the first content system;based on determining that the security specifications associated with the second content system meet the security requirements associated with the first content system, send, to the first content system, a security approval indication; andbased on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, send, to the first content system, a security denial indication.12. The system of item 11, wherein the control circuitry is further configured to:based on receiving the indication of anticipated data exchange and the second security profile associated with the second content system, send, from the security verification system, a verification request to the second content system; andreceive, from the second content system, a response to the verification request; wherein determining whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the response to the verification request.13. The system of item 12, wherein:the verification request comprises an application programming interface (API) request; andthe response to the verification request comprises and API response.14. The system of item 11, whereinthe first security profile includes historical instances of data exchanges between the first content system and a third content system, andthe control circuitry is configured to determine whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the historical instances of data exchanges between the first content system and the third content system.15. The system of item 14, wherein the control circuitry is further configured to:retrieve a third security profile associated with the third content system, wherein the third security profile comprises security specifications associated with the third content system; andprior to sending the verification request to the second content system, modify the verification request based on the third security profile.16. The system of item 11, wherein the control circuitry is further configured to:display, at a user interface accessible by the first content system, the second content system, or the security verification system, information related to the first security profile, the second security profile, the security approval indication, or the security denial indication.17. The system of item 11, wherein the control circuitry is further configured to:based on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, identify, based on the first security profile, a security requirement of a plurality of security requirements of the first security profile that is not implemented at the second content system; andsend, to the second content system, an instruction to implement the identified security requirement.18. The system of item 11, wherein the control circuitry is further configured to:based on the indication of anticipated data exchange between the first content system and the second content system, determine a type of data that is anticipated to be exchanged between the first content system and the second content system; andbased on the determined type of data:update the security requirements associated with the first content system; andsend, from the security verification system, a recommendation to update the security specifications associated with the second content system.19. The system of item 11, wherein:the first security profile includes historical instances of data exchanges between the second content system and a third content system, andwherein the control circuitry is further configured to:determine whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the historical instances of data exchanges between the second content system and the third content system.20. The system of item 11, wherein the second content system is a content system of a plurality of content systems, each comprising respective security profiles, the control circuitry is further configured to:determine, for each of the plurality of content systems, a respective security level;determine, based on the first security profile, a threshold security level; and comparing each of the respective security levels of each of the plurality of content systems to the determined threshold security level; andwherein the security denial indication is further based on determining that the security level of any one of the plurality of content systems does not meet the determined threshold security level.21. A non-transitory computer readable medium comprising instructions that when executed by control circuitry causes the control circuitry to:retrieve, at a security verification system, an indication of anticipated data exchange between a first content system and a second content system;based on receiving the indication of anticipated data exchange, retrieve a first security profile associated with the first content system and a second security profile associated with the second content system, wherein the first security profile comprises security requirements associated with the first content system, and the second security profile comprises security specifications associated with the second content system;determine, based on the first security profile and the second security profile, whether the security specifications associated with the second content system meet the security requirements associated with the first content system;based on determining that the security specifications associated with the second content system meet the security requirements associated with the first content system, send, to the first content system, a security approval indication; andbased on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, send, to the first content system, a security denial indication.22. The non-transitory computer readable medium of item 21, further comprising instructions that when executed by the control circuitry cause the control circuitry to:based on receiving the indication of anticipated data exchange and the second security profile associated with the second content system, send, from the security verification system, a verification request to the second content system; andreceive, from the second content system, a response to the verification request; wherein determining whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the response to the verification request.23. The non-transitory computer readable medium of item 22, wherein:the verification request comprises an application programming interface (API) request; andthe response to the verification request comprises and API response.24. The non-transitory computer readable medium of item 21, wherein:the first security profile includes historical instances of data exchanges between the first content system and a third content system, andthe control circuitry is configured to determine whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the historical instances of data exchanges between the first content system and the third content system.25. The non-transitory computer readable medium of item 24, further comprising instructions that when executed by the control circuitry cause the control circuitry to:retrieve a third security profile associated with the third content system, wherein the third security profile comprises security specifications associated with the third content system; andprior to sending the verification request to the second content system, modify the verification request based on the third security profile.26. The non-transitory computer readable medium of item 21, further comprising instructions that when executed by the control circuitry cause the control circuitry to:display, at a user interface accessible by the first content system, the second content system, or the security verification system, information related to the first security profile, the second security profile, the security approval indication, or the security denial indication.27. The non-transitory computer readable medium of item 21, further comprising instructions that when executed by the control circuitry cause the control circuitry to:based on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, identify, based on the first security profile, a security requirement of a plurality of security requirements of the first security profile that is not implemented at the second content system; andsend, to the second content system, an instruction to implement the identified security requirement.28. The non-transitory computer readable medium of item 21, further comprising instructions that when executed by the control circuitry cause the control circuitry to:based on the indication of anticipated data exchange between the first content system and the second content system, determine a type of data that is anticipated to be exchanged between the first content system and the second content system; andbased on the determined type of data:update the security requirements associated with the first content system; and send, from the security verification system, a recommendation to update the security specifications associated with the second content system.29. The non-transitory computer readable medium of item 21, wherein:the first security profile includes historical instances of data exchanges between the second content system and a third content system, andfurther comprising instructions that when executed by the control circuitry cause the control circuitry to:determine whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the historical instances of data exchanges between the second content system and the third content system.30. The non-transitory computer readable medium of item 21, wherein the second content system is a content system of a plurality of content systems, each comprising respective security profiles, further comprising instructions that when executed by the control circuitry cause the control circuitry to:determine, for each of the plurality of content systems, a respective security level;determine, based on the first security profile, a threshold security level; and comparing each of the respective security levels of each of the plurality of content systems to the determined threshold security level; andwherein the security denial indication is further based on determining that the security level of any one of the plurality of content systems does not meet the determined threshold security level.

[0171] While some portions of this disclosure may refer to “convention” or examples, any such reference is merely to provide context to the instant disclosure and does not form any admission as to what constitutes the state of the art. Accordingly, this description is to be taken only by way of example and not to otherwise limit the scope of the exemplary embodiments herein. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the exemplary embodiments herein.

Claims

AMENDED CLAIMSreceived by the International Bureau on 22 July 2026 (22.07.2026)We claim:

1. A method comprising:receiving, at a security verification system, an indication of anticipated data exchange between a first content system and a second content system;based on receiving the indication of anticipated data exchange, retrieving a first security profile associated with the first content system and a second security profile associated with the second content system, wherein the first security profile comprises security requirements associated with the first content system, and the second security profile comprises security specifications associated with the second content system;determining, based on the first security profile and the second security profile, whether the security specifications associated with the second content system meet the security requirements associated with the first content system;based on determining that the security specifications associated with the second content system meet the security requirements associated with the first content system, sending, to the first content system, a security approval indication; andbased on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, sending, to the first content system, a security denial indication.

2. The method of claim 1, further comprising:based on receiving the indication of anticipated data exchange and the second security profile associated with the second content system, deploying, by the security verification system, one or more agents that send a verification request to the second content system, the verification request querying the second content system for one or more endpoint security parameters of a plurality of registered endpoints managed by the second content system, the one or more endpoint security parameters including whether a security application is deployed at each of the plurality of registered endpoints and whether each of the plurality of registered endpoints checks in within a predetermined interval; andreceiving, from the second content system and by the one or more agents, a response to the verification request indicating the one or more endpoint security parameters;aggregating, by the security verification system, the response into a verification result; wherein determining whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the verification result.

3. The method of claim 2, whereinthe verification request comprises an application programming interface (API) request; andthe response to the verification request comprises an API response.

4. The method of claim 1, whereinthe first security profile includes historical instances of data exchanges between the first content system and a third content system, anddetermining whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the historical instances of data exchanges between the first content system and the third content system.

5. The method of claim 4, further comprising:retrieving a third security profile associated with the third content system, wherein the third security profile comprises security specifications associated with the third content system; andprior to sending a verification request to the second content system, modifying the verification request based on the third security profile.

6. The method of claim 1, further comprising:displaying, at a user interface accessible by the first content system, the second content system, or the security verification system, information related to the first security profile, the second security profile, the security approval indication, or the security denial indication.

7. The method of claim 1, further comprising:based on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, identifying, based on the first security profile, a security requirement of a plurality of security requirements of the first security profile that is not implemented at the second content system;determining whether an alternative security specification of the second content system provides functionality or protection sufficiently similar to the identified security requirement;sending, to the second content system, an instruction to implement the identified security requirement; andreceiving, at the security verification system and from the first content system, data of the anticipated data exchange, and storing the data at the security verification system until the security specifications associated with the second content system meet the security requirements associated with the first content system.

8. The method of claim 1, further comprising:based on the indication of anticipated data exchange between the first content system and the second content system, determining a type of data that is anticipated to be exchanged between the first content system and the second content system;based on the determined type of data:updating the security requirements associated with the first content system; and sending, from the security verification system, a recommendation to update the security specifications associated with the second content system.

9. The method of claim 1, whereinthe first security profile includes historical instances of data exchanges between the second content system and a third content system, anddetermining whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the historical instances of data exchanges between the second content system and the third content system.

10. The method of claim 1, wherein the second content system is a content system of a plurality of content systems, each comprising respective security profiles, the method further comprising:deploying, by the security verification system, a plurality of agents that concurrently query each of the plurality of content systems for security data;generating, based on the security data, a respective verification result for each of the plurality of content systems;determining, for each of the plurality of content systems, a respective security level, wherein the respective security level is determined by a scoring instruction generated based on the respective verification result;determining, based on the first security profile, a threshold security level; and comparing each of the respective security levels of each of the plurality of content systems to the determined threshold security level;wherein the security denial indication is further based on determining that the security level of any one of the plurality of content systems does not meet the determined threshold security level.

11. A system comprising:control circuitry configured to:retrieve, at a security verification system, an indication of anticipated data exchange between a first content system and a second content system;based on receiving the indication of anticipated data exchange, retrieve a first security profile associated with the first content system and a second security profileassociated with the second content system, wherein the first security profile comprises security requirements associated with the first content system, and the second security profile comprises security specifications associated with the second content system;determine, based on the first security profile and the second security profile, whether the security specifications associated with the second content system meet the security requirements associated with the first content system;based on determining that the security specifications associated with the second content system meet the security requirements associated with the first content system, send, to the first content system, a security approval indication; andbased on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, send, to the first content system, a security denial indication.

12. The system of claim 11, wherein the control circuitry is further configured to:based on receiving the indication of anticipated data exchange and the second security profile associated with the second content system, deploy, by the security verification system, one or more agents that send a verification request to the second content system, the verification request querying the second content system for one or more endpoint security parameters of a plurality of registered endpoints managed by the second content system, the one or more endpoint security parameters including whether a security application is deployed at each of the plurality of registered endpoints and whether each of the plurality of registered endpoints checks in within a predetermined interval; andreceive, from the second content system and by the one or more agents, a response to the verification request indicating the one or more endpoint security parameters; and aggregate, by the security verification system, the response into a verification result; wherein determining whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the verification result.

13. The system of claim 12, wherein:the verification request comprises an application programming interface (API) request; andthe response to the verification request comprises an API response.

14. The system of claim 11, whereinthe first security profile includes historical instances of data exchanges between the first content system and a third content system, andthe control circuitry is configured to determine whether the security specifications associated with the second content system meet the security requirements associated with thefirst content system is further based on the historical instances of data exchanges between the first content system and the third content system.

15. The system of claim 14, wherein the control circuitry is further configured to:retrieve a third security profile associated with the third content system, wherein the third security profile comprises security specifications associated with the third content system; andprior to sending a verification request to the second content system, modify the verification request based on the third security profile.

16. The system of claim 11, wherein the control circuitry is further configured to:display, at a user interface accessible by the first content system, the second content system, or the security verification system, information related to the first security profile, the second security profile, the security approval indication, or the security denial indication.

17. The system of claim 11, wherein the control circuitry is further configured to:based on determining that the security specifications associated with the second content system do not meet the security requirements associated with the first content system, identify, based on the first security profile, a security requirement of a plurality of security requirements of the first security profile that is not implemented at the second content system;determine whether an alternative security specification of the second content system provides functionality or protection sufficiently similar to the identified security requirement;send, to the second content system, an instruction to implement the identified security requirement; andreceive, at the security verification system and from the first content system, data of the anticipated data exchange, and store the data at the security verification system until the security specifications associated with the second content system meet the security requirements associated with the first content system.

18. The system of claim 11, wherein the control circuitry is further configured to:based on the indication of anticipated data exchange between the first content system and the second content system, determine a type of data that is anticipated to be exchanged between the first content system and the second content system; andbased on the determined type of data:update the security requirements associated with the first content system; and send, from the security verification system, a recommendation to update the security specifications associated with the second content system.

19. The system of claim 11, whereinthe first security profile includes historical instances of data exchanges between the second content system and a third content system, andthe control circuitry is configured to determine whether the security specifications associated with the second content system meet the security requirements associated with the first content system is further based on the historical instances of data exchanges between the second content system and the third content system.

20. The system of claim 11, wherein the second content system is a content system of a plurality of content systems, each comprising respective security profiles, the control circuitry is further configured to:deploy, by the security verification system, a plurality of agents that concurrently query each of the plurality of content systems for security data;generate, based on the security data, a respective verification result for each of the plurality of content systems;determine, for each of the plurality of content systems, a respective security level, wherein the respective security level is determined by a scoring instruction generated based on the respective verification result;determine, based on the first security profile, a threshold security level; and comparing each of the respective security levels of each of the plurality of content systems to the determined threshold security level; andwherein the security denial indication is further based on determining that the security level of any one of the plurality of content systems does not meet the determined threshold security level.

Images