Signal Conditions

A Signal Policy has one or more rules, where each rule has a Trigger Condition that defines conditions for reporting an event, and optional actions to take if an event is reported. A trigger condition can be a simple or complex logical expression that’s comprised of multiple, more focused conditions.

Below we are going to walk you through some of our best practices for using different Signal Trigger Conditions

 

1. Signal Policy: Personal Identifiable Information (PII)


This specific rule is working to identify any instance of shared Address Information

Condition Statements:

  • AND Condition > Patterns > United States Zip code

  • AND Condition > Keywords > Street Suffix

  • NOT Condition > Patterns > URL

Understanding the Condition Statements:

This Signal policy will identify any United States Zip code patterns and Street Suffix keywords, but will not identify URL patterns.

TIP: This statement condition has helped health care organizations stay HIPPA compliant and avoid regulatory fines/penalties.

 

2. Signal Policy: Sensitive Financial Information


This specific rule is working to identify any instance of shared Credit Card numbers

Condition Statements:

  • AND Condition > Credit Card Number (Luhn Algorithm)

  • NOT Condition > Patterns > URL

Understanding the Condition Statements:

This Signal policy will identify any Credit Card Numbers based off a Luhn Algorithm, but will not identify URL Patterns.

TIP: This statement condition has helped banking companies remove private data off of their collaboration platforms and stay compliant with industry regulations such as FINRA.

 

3. Signal Policy: Workplace Security


This specific rule is working to identify any instance of leaked Intellectual Property (Code)

Condition Statements:

  • AND Condition > Keywords > Create Custom Keyword Template > Sensitive Project Keywords

  • AND Condition > Code Detection

Understanding the Condition Statements:

This Signal policy will identify any sensitive project keywords and detect code using our code detection model. The Model currently identifies SQL, JavaScript, Excel, or JSON code snippets. It is trained to identify messages as either Code or Not Code and operates at a 92% accuracy rate.

TIP: This statement condition helps ensure Data Loss Prevention (DLP) is in place when collaborating about trade marked data.

 

4. Signal Policy: Labor Relations


This specific rule is working to identify any instance of Disgruntled Employees

Condition Statements:

  • AND Condition > Keywords > Salary

  • AND Condition > Toxic Speech or Negative Sentiment

Understanding the Condition Statements:

This Signal policy will identify salary keywords being used in a toxic way or with negative sentiment.

TIP: This statement condition can help companies gain visibility into how their hourly-based employees are feeling regarding their working conditions (e.g. pay rate). This can help avoid potential employee burnout and internal conflict.

 

5. Signal Policy: Sexual Content

This specific policy is working to identify any instance of sexual content

Condition Statements:

  • AND Condition > Keywords > Sexual Orientation

  • OR Condition > Keywords > Sexual Orientation Slurs

  • AND Condition > Toxic Speech or Negative Sentiment

Understanding the Condition Statements:

This Signal rule will identify any sexual orientation keywords or slurs being used in a toxic way or with negative sentiment

TIP: This statement condition can help Human Resource teams quickly identify and investigate individuals or groups that are involved in the inappropriate incident and take proper action.

 

6. Signal Policy: Sensitive Files/Extensions 

This specific policy is working to identify any instance where a file name, containing specific characters, has been shared across a collaboration platform. 

Condition Statements: 

  • AND Conditions > File Names and Extensions 

Understanding the Condition Statement: 

This Signal Rule will capture any files that contain sensitive information like PII, personnel data, organizational financial information, or proprietary designs or code that should not be shared. 

TIP: This statement condition can help protect an organization's valuable intellectual property and work to prevent privacy, security and regulatory-related risks.

 

Top Used Signal Policies:

Listed below are some of the top Signal Policies we've seen implemented by other Aware customers.  

Risk Intelligence Signal Policies 

  • Password Detection 
  • Credit Card Numbers 
  • Social Security Numbers (SNN)
  • Personal Identifiable Information (PII)
  • Confidential/Sensitive Project Information

Organizational Intelligence Signal Policies 

  • Acceptable Usage (Profanity/Harassment)
  • Employee Recognition 
  • Internal Change Employee Reaction (restructure, new business objectives, employee retention etc..)