...
CyberSage supports the threat modeling methodology, where the threat model are is derived from business values and the threats to these values.
...
Customize threat modeling profiles for enterprise' specific business and risk profile
business and risk profile can be different in each enterprise. It is possible that the out-of-box threat modeling profile needs to adjust to fit the specific scenarios of an enterprise.
CyberSage’s threat modeling engine supports changes in these profiles with rule changes in its rule interface. The rule changes are independent from CyberSage core software and do not require skillset of professional software developerstherefore can be done quickly.
update existing threat modeling profile
...
When the enterprise has unique business features that are not supported by the out-of-box profiles, new profiles can be created with the rule engine and new rules.
Embed security into
...
development life-cycle management
CyberSage enables IT(information technology) teams, such as software development and other IT design/build team to make the threat modeling and remediation part of their development life-cycle. This allows the prevention or remediation of security weakness starts early in the life-cycle, reduces security risks and remediation costs.
...
it facilitates further analysis of security weaknesses that depends on the causing factors which enables the attack vectors.
Automate
...
security issue risk rating
...
Organizations need to assign risk rating to identified security weakness (vulnerabilities) in order to prioritize the remediation based on the risk. The security vulnerability risk rating needs to be contextualized to the organization's business profile. For instance, a vulnerability resulting in information disclosure should have much higher risk rating in an military organization than the same one in a social media application.
The risk rating also needs to follow an established methodology such as operational risk management(ORM).
...
and threat impact analysis aligned with enterprise’s business profile
The threat modeling engine uses the risk and business profile (e.g, confidential requirements of an application) as threat modeling input. It also automates the risk rating with ORM (operational risk management) model and incorporate both the impact and likelihood of identified security weakness.
Automate business impact rating of security threats contextualized for the business model of the organization.
The organizations need to associate the security weakness identified in security risk analysis with impact to its business so they can make risk based decisions, as impact is half of the equation of proper risk rating.
The same technical security weakness may have very different business impact, depending on what business functionalities the vulnerable components supports. For instance, the same cross-site-scripting (XSS) vulnerability will have very different impact for customer login page of an online banking portal than a bbs page.
Most of the security tools that identifies security weaknesses (e,g, vulnerability scanner) does not include business impact in their out-of-box risk rating method. Further more, most of them does not provide capability to contextualize risk rating with business impact. Such cookie-cutter risk rating does not help the organizations to prioritize the remediation.
CyberSage incorporate threat and impact analysis of IT assets in security issue risk rating in two ways:
associate security weakness to the business impact specific to the organization.
CyberSage associate business impacts with a given threat for a business feature. For instance, for a business feature in a web application where customers can update their profile, one of the threats (attacker's goal) is to access sensitive information in the unauthorized customer profiles. The business impact associated with the threat is disclosure of sensitive information.
.
Please see details here.
CyberSage further establish the rating for the business impacts, using the business and risk attributes of the organization. For instance, for a social media application, compromise of the information in the customer profile may cause less impact to the organization than the same compromise for a banking application, due to the fact that banking customer's information can be used for financial fraud and are under strict laws and regulations.
...