Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Governance, Risk, and Compliance
Table of Contents
Choose your release version
    Home Orlando Governance, Risk, and Compliance Governance, Risk, and Compliance Risk Management Understanding Risk Management Advanced Risk Assessment Factors in Advanced Risk Assessment

    Factors in Advanced Risk Assessment

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Factors in Advanced Risk Assessment

    Factors are questions that you can use to analyze risks. Factors appear on a risk assessment instance.

    Factors are questions that appear during the risk assessment. To use Advanced Risk Assessment, you must first define these factors and configure a risk assessment methodology (RAM). For more information on RAMs, see Configure a risk assessment methodology. Each factor or question has a response. There are different types of factors:
    • Manual factor: A factor that requires human input. The response is a manual response. An example is your name.
    • Automated factor: A factor whose response is automatically calculated. An example is the temperature in your city today. The information is fetched from external sources.
    • Scripted automated factors: A factor that is used to write scripts.
    • Group factor: A set of factors that are grouped logically.

    These factor types are explained more in the following sections. After you define the factors and publish them, you can configure a RAM and associate the factors to the assessment types within the RAM. The RAM forms the basis of the risk assessment. Publish each of the selected assessment types, and then publish the RAM. Users with the sn_risk.user role can select the assessment types for which the assessment must be performed.

    Your risk assessment instance is then created. Its properties depend on the assessment types and options that you selected for your RAM. The risk assessment instance is where the risk assessor evaluates the risks. As a question, a factor can be used in multiple assessment types. For example, a question such as "What is the probability of a building getting flooded?" can be a part of either an inherent assessment or a residual assessment after the control effectiveness assessment.

    Note: A factor can be used in multiple assessment types, but it can be used in only one RAM. A factor that is created and used in one RAM cannot be reused in other RAMs.

    Types of factor contributions

    An assessor provides responses to factors. Risk assessors can contribute to factors in the following ways:
    • Qualitative: Losses are in the form of subjective terms such as high, medium, and low. The losses can also be in the form of a numerical score that is converted into a rating.
    • Quantitative: Losses are in a numerical form. They can be incurred from a risk in monetary terms. They contribute to the inherent Annual Loss Expectancy (ALE).
    • Both: Losses have both a qualitative risk rating and a quantitative dollar value. These ratings are also called semi-quantitative.
    For more information on understanding qualitative, quantitative, and semi-quantitative ratings, see Types of risk rating methodologies

    Manual factors

    In a risk assessment, questions that need human responses from the respondents are called manual factors. In manual factors, the response is subjective and difficult to classify. Some questions require human intelligence and assessment. Therefore, a manual factor is a subjective assessment of a person's view. Examples of manual factors are reputational impact, expected speed of onset, and so on. In manual factors, users can provide the following types of responses:
    • Text: A descriptive answer. For example, feedback. This choice does not contribute toward the risk score calculation​.
    • Choice: User-defined choices to the questions in the assessment. For example, users can select risk ratings from low, medium, or high.
    • Number: A numeric value. For example, the number of open issues.
    • Currency: An amount in the local currency of the user. For example, the financial impact of a certain risk.
    • Percentage: A percentage value for the questions in the assessment. For example, the percentage of employees satisfied with the organization strategies.

    Group factors

    When factors are grouped logically, they are called group factors. A group factor's score depends on the responses of the corresponding manual factors​. For example, organizations are affected from financial risks and non-financial risks. You can create some factors for financial risks, and other factors for non-financial risks. You can combine these two sets of factors into a single group factor called Overall Impact. Like manual factors, group factors can contribute either to a numerical risk score that is converted to a qualitative contribution, or to the ALE values as a quantitative contribution.

    Automated factors

    Automated factors automatically fetch data from any of the data sources such as tables or database views. Automated factors help to automate the risk assessment process. They do not rely on manual inputs, and thus reduce subjectivity. For example, a risk assessor wants to perform an assessment for different locations. One of the automated factors is the political condition of a country, and this information is publicly available on a website. Because this data does not reside within ServiceNow, the assessor can use automated factors to fetch the data. Some other examples of automated factors are the following:
    • The number of employees on a project.
    • The revenue of a business unit.
    • The business criticality of a process.

    Scripted automated factors

    Automated scripted factors are used to write scripts. The scripts fetch the data from either ServiceNow records or from external sources. Scripted automated factors automatically provide the responses for factors during risk assessment.

    The following use cases demonstrate an example of how you can model scripted factors. For example, if you want to use the results from the compliance function to assess the mitigation effectiveness of the controls, there are two ways for assessing the controls:
    • Individual assessment of controls
    • Control environment assessment.
    In the individual assessment of controls, each control is separately assessed. To understand control assessment in the context of scripted factors, consider the example of money laundering as a risk. In this example, the control effectiveness is assessed based on the percentage of the failed controls. The values of the failed controls are then transformed into a rating to calculate the control effectiveness of that control. For example, the risk of money laundering has three mitigating controls:
    • Employee training
    • Internal audit on employees
    • Customer due diligence
    Assume that you have defined the control effectiveness criteria in the following manner:
    Control Design Effectiveness Failure Control Effectiveness
    0%-30% Effective
    30%-60% Needs improvement
    > 60% Ineffective

    Now, assume that out of the three controls, one control passed and two controls failed. The failure of two controls translates into a 66.67% failure rate. Based on the transformation and based on the previous table, the control effectiveness rating is ineffective. You can use this defined script to automate the response to the factor to assess the risk of money laundering.

    As for control environment assessment, you can assess the complete control environment instead of assessing each control individually. To understand control environment assessment, consider the following example. Assume that you want to assess the control environment based on two aspects: design effectiveness and operating effectiveness. To calculate the design effectiveness, you can fetch the related controls that are related to the risk of money laundering. You can then look at the test results to understand how many of the controls had failed. Assume that you have defined the control effectiveness criteria in the following manner:
    Control Design Effectiveness Failure Control Effectiveness
    0%-30% Effective
    30%-60% Needs improvement
    > 60% Ineffective

    Now, assume that two controls failed and one control passed. Thus, the control design effectiveness failure rate is 33.33%. Based on the previous table, this low value of 33.33% means that the control design needs improvement. This response can be automatically scripted in the automated scripted factor because it does not need any human calculation or intervention.

    Related tasks
    • Create a manual factor
    • Create a group factor
    • Create an automated factor
    • Create a scripted automated factor
    • Configure a risk assessment methodology
    • Copy a risk assessment methodology
    • Retire a risk assessment methodology
    • Configure an inherent assessment
    • Configure a control effectiveness assessment
    • Configure residual assessment
    • Create risk color styles
    • Configure risk heatmaps
    • Create a risk assessment scope and initiate assessments
    Related concepts
    • Workflow of Advanced Risk Assessment
    • Types of risk rating methodologies
    • Understanding the risk assessment instance
    • Manage risk assessment scheduler
    • Integration of advanced risk assessments with risks and controls
    • Advanced risk assessment dashboard
    • Risk score rollup in advanced risk assessment

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Factors in Advanced Risk Assessment

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Factors in Advanced Risk Assessment

      Factors are questions that you can use to analyze risks. Factors appear on a risk assessment instance.

      Factors are questions that appear during the risk assessment. To use Advanced Risk Assessment, you must first define these factors and configure a risk assessment methodology (RAM). For more information on RAMs, see Configure a risk assessment methodology. Each factor or question has a response. There are different types of factors:
      • Manual factor: A factor that requires human input. The response is a manual response. An example is your name.
      • Automated factor: A factor whose response is automatically calculated. An example is the temperature in your city today. The information is fetched from external sources.
      • Scripted automated factors: A factor that is used to write scripts.
      • Group factor: A set of factors that are grouped logically.

      These factor types are explained more in the following sections. After you define the factors and publish them, you can configure a RAM and associate the factors to the assessment types within the RAM. The RAM forms the basis of the risk assessment. Publish each of the selected assessment types, and then publish the RAM. Users with the sn_risk.user role can select the assessment types for which the assessment must be performed.

      Your risk assessment instance is then created. Its properties depend on the assessment types and options that you selected for your RAM. The risk assessment instance is where the risk assessor evaluates the risks. As a question, a factor can be used in multiple assessment types. For example, a question such as "What is the probability of a building getting flooded?" can be a part of either an inherent assessment or a residual assessment after the control effectiveness assessment.

      Note: A factor can be used in multiple assessment types, but it can be used in only one RAM. A factor that is created and used in one RAM cannot be reused in other RAMs.

      Types of factor contributions

      An assessor provides responses to factors. Risk assessors can contribute to factors in the following ways:
      • Qualitative: Losses are in the form of subjective terms such as high, medium, and low. The losses can also be in the form of a numerical score that is converted into a rating.
      • Quantitative: Losses are in a numerical form. They can be incurred from a risk in monetary terms. They contribute to the inherent Annual Loss Expectancy (ALE).
      • Both: Losses have both a qualitative risk rating and a quantitative dollar value. These ratings are also called semi-quantitative.
      For more information on understanding qualitative, quantitative, and semi-quantitative ratings, see Types of risk rating methodologies

      Manual factors

      In a risk assessment, questions that need human responses from the respondents are called manual factors. In manual factors, the response is subjective and difficult to classify. Some questions require human intelligence and assessment. Therefore, a manual factor is a subjective assessment of a person's view. Examples of manual factors are reputational impact, expected speed of onset, and so on. In manual factors, users can provide the following types of responses:
      • Text: A descriptive answer. For example, feedback. This choice does not contribute toward the risk score calculation​.
      • Choice: User-defined choices to the questions in the assessment. For example, users can select risk ratings from low, medium, or high.
      • Number: A numeric value. For example, the number of open issues.
      • Currency: An amount in the local currency of the user. For example, the financial impact of a certain risk.
      • Percentage: A percentage value for the questions in the assessment. For example, the percentage of employees satisfied with the organization strategies.

      Group factors

      When factors are grouped logically, they are called group factors. A group factor's score depends on the responses of the corresponding manual factors​. For example, organizations are affected from financial risks and non-financial risks. You can create some factors for financial risks, and other factors for non-financial risks. You can combine these two sets of factors into a single group factor called Overall Impact. Like manual factors, group factors can contribute either to a numerical risk score that is converted to a qualitative contribution, or to the ALE values as a quantitative contribution.

      Automated factors

      Automated factors automatically fetch data from any of the data sources such as tables or database views. Automated factors help to automate the risk assessment process. They do not rely on manual inputs, and thus reduce subjectivity. For example, a risk assessor wants to perform an assessment for different locations. One of the automated factors is the political condition of a country, and this information is publicly available on a website. Because this data does not reside within ServiceNow, the assessor can use automated factors to fetch the data. Some other examples of automated factors are the following:
      • The number of employees on a project.
      • The revenue of a business unit.
      • The business criticality of a process.

      Scripted automated factors

      Automated scripted factors are used to write scripts. The scripts fetch the data from either ServiceNow records or from external sources. Scripted automated factors automatically provide the responses for factors during risk assessment.

      The following use cases demonstrate an example of how you can model scripted factors. For example, if you want to use the results from the compliance function to assess the mitigation effectiveness of the controls, there are two ways for assessing the controls:
      • Individual assessment of controls
      • Control environment assessment.
      In the individual assessment of controls, each control is separately assessed. To understand control assessment in the context of scripted factors, consider the example of money laundering as a risk. In this example, the control effectiveness is assessed based on the percentage of the failed controls. The values of the failed controls are then transformed into a rating to calculate the control effectiveness of that control. For example, the risk of money laundering has three mitigating controls:
      • Employee training
      • Internal audit on employees
      • Customer due diligence
      Assume that you have defined the control effectiveness criteria in the following manner:
      Control Design Effectiveness Failure Control Effectiveness
      0%-30% Effective
      30%-60% Needs improvement
      > 60% Ineffective

      Now, assume that out of the three controls, one control passed and two controls failed. The failure of two controls translates into a 66.67% failure rate. Based on the transformation and based on the previous table, the control effectiveness rating is ineffective. You can use this defined script to automate the response to the factor to assess the risk of money laundering.

      As for control environment assessment, you can assess the complete control environment instead of assessing each control individually. To understand control environment assessment, consider the following example. Assume that you want to assess the control environment based on two aspects: design effectiveness and operating effectiveness. To calculate the design effectiveness, you can fetch the related controls that are related to the risk of money laundering. You can then look at the test results to understand how many of the controls had failed. Assume that you have defined the control effectiveness criteria in the following manner:
      Control Design Effectiveness Failure Control Effectiveness
      0%-30% Effective
      30%-60% Needs improvement
      > 60% Ineffective

      Now, assume that two controls failed and one control passed. Thus, the control design effectiveness failure rate is 33.33%. Based on the previous table, this low value of 33.33% means that the control design needs improvement. This response can be automatically scripted in the automated scripted factor because it does not need any human calculation or intervention.

      Related tasks
      • Create a manual factor
      • Create a group factor
      • Create an automated factor
      • Create a scripted automated factor
      • Configure a risk assessment methodology
      • Copy a risk assessment methodology
      • Retire a risk assessment methodology
      • Configure an inherent assessment
      • Configure a control effectiveness assessment
      • Configure residual assessment
      • Create risk color styles
      • Configure risk heatmaps
      • Create a risk assessment scope and initiate assessments
      Related concepts
      • Workflow of Advanced Risk Assessment
      • Types of risk rating methodologies
      • Understanding the risk assessment instance
      • Manage risk assessment scheduler
      • Integration of advanced risk assessments with risks and controls
      • Advanced risk assessment dashboard
      • Risk score rollup in advanced risk assessment

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login