Evident Security Platform Custom Signatures Samples
Ruby JavaScript
Failed to load latest commit information.
README.md added comment to services Jul 21, 2015
ec2_cis_ami_amazon_linux_2014_09.js adding benchmark link Mar 28, 2015
ec2_cis_ami_centos_7.js adding benchmark link Mar 28, 2015
ec2_cis_ami_microsoft_windows_2012_r2.js adding benchmark link Mar 28, 2015
ec2_cis_ami_rhel_6.js adding benchmark link Mar 28, 2015
ec2_cis_ami_rhel_7.js adding benchmark link Mar 28, 2015
ec2_cis_ami_ubuntu.js adding benchmark link Mar 28, 2015
ec2_enforce_volume_type.js docs for js sigs Feb 23, 2015
ec2_global_ssh_with_public.rb added new signature Dec 17, 2015
ec2_golden_ami.js added region mapping Dec 18, 2014
ec2_instance_age.js Update file reference in ec2_instance_age header Aug 31, 2015
ec2_instance_maintenance_event_check.rb inspecting date of maintenance to generate FAIL within 7 days Nov 1, 2016
ec2_instance_name_tag_check.js created initial version Apr 8, 2015
ec2_instance_profile_name_check.rb fixed comments May 21, 2015
ec2_no_tags.js formatting and configuration updates Feb 23, 2015
ec2_only_micro.js formatting and configuration updates Feb 23, 2015
ec2_public_ami.rb Added ec2_public_ami.rb Jan 15, 2016
ec2_unencrypted_ami.rb new signature Jan 8, 2016
elastic_search_open_access_policy.rb Improved handling for policies with multiple statements Jan 18, 2017
elb_cert_expiry.rb added days_left to deep_inspection May 20, 2015
elb_imperfect_forward_secrecy.rb for real now Oct 22, 2015
elb_logjam_check.rb added AWS forum link to comment May 22, 2015
glo_instance_counts.rb added conditional to throw warn if >0 or pass if =0 Nov 3, 2015
iam_access_keys_last_used.rb added access_key_metadata struct to length check Aug 18, 2015
iam_check_interactive_mfa_users.rb fixed comments May 21, 2015
iam_password_policy_check.rb Update iam_password_policy_check.rb Nov 10, 2016
inspector_describe_findings.rb Added sample Inspector findings signature Oct 5, 2016
rds_global_mysql.rb added a conditional to check for db_name and return a valid resource_id Sep 18, 2015
rds_public_access.rb Added new Customer Signature for RDS Mar 31, 2016
s3_bucket_acl_exception.rb added new s3 bucket acl sig Sep 23, 2015
s3_bucket_policy.rb new ruby custom sig Apr 17, 2015
s3_logging.js changed to confirm to current sig spec Apr 15, 2015


Custom Signatures

This is a repo of custom signature samples that you can use in your environment.

Source code files are provided for demonstration purposes only.

Please email support@evident.io if you have any questions.

Custom Signature Tutorial ( javascript )


A custom signature is a function that reads AWS SDK data from Amazon, and creates one or more alerts based on that data and conditionals you describe.

An alert has

  • a status of pass fail warn or error
  • identifying metadata such as instance_id or logging_status
  • This field is used to identify unique alerts that share the same signature but describe different AWS resources (ex. volume_id instance_id bucket_name)

A custom signature will always have two sections config and perform.

In the config section you define the parameters your signature will use when it runs. For example, you set which region you are interested in checking, and you give the signature a unique id.

In the perform section you write a function that implements your security policy, and creates one or more alerts. The alerts are themselves are created using the dsl.pass() and dsl.fail() functions. Take those objects returned by the functions and push them onto an array of alerts. When you are done return them at the end of the perform block. Each alert is then stored in the database.


An example config section

dsl.configure(function(c) {
  c.valid_regions = ['us_east_1'];
  c.identifier = 'AWS:EC2-909'
  c.deep_inspection = ['volume_type', 'volume_id'];
  c.unique_identifier = ['volume_id'];

dsl.configure is a function that is passed an anonymous callback function that receives a configuration object (here c) as the first argument. Inside the anonymous function you have access the configuration settings for the signature.

configuration metadata


  • An array of regions to run the signature
  • ex. ['us_east_1', 'us_west_2']


  • A unique string identifying the signature in the database. Usually takes the form AWS:SERVICE_CODE-SOME_NUMBER
  • ex. AWS:EC2-303 or AWS:R52:909


  • An array of fields that provide additional information beyond the status when an alert is viewed in the actual report.
  • These fields are referenced in the perform block when you call dsl.set_data()


  • An array of fields that are used to identify the alert as unique in the database.
  • This is commonly unique to the resource being described in the alert.


The perform section is a function that is passed the AWS SDK as an object. You use this aws object to make calls to AWS.

Perform block psuedocode looks like

function perform(aws){
  try {

    // make a container for returned alerts
    var alerts = []

    // make some AWS calls to get an array of resources
    // for each resource
    // {
    //    read some resource information using the aws object passed to the
    //    perform function
    //    store some of that resource information to the report using
    //    dsl.set_data()
    //    compare it to a desired value or state
    //      push a dsl.pass() or dsl.fail() to the alerts container
    //        ex. alerts.push(dsl.fail({message:'failed'}))
    // }

    return alerts;

  } catch(err){
    return dsl.error({
      errors: err.message

An example perform section:

function perform(aws) {
  try {

    // make the container for returned alerts
    var alerts = [];

    var region = aws.region;

    // these are AWS SDK calls to get a list of resources to check
    var volumes = aws.ec2.describe_volumes().volumes;

    // this is our condition we are searching for in this signature
    // we want to enforce a specific volume type in this region
    // if you change the variable below to 'gp2' it will use that
    var type_to_check_for = 'standard'

    // for each volume returned from the AWS SDK call
    volumes.map(function(volume) {

      // this is where you specify the data for the fields listed in the
      // deep_inspection array
      // create an object and give it some information
      var report = {
        volume_type: volume.volume_type,
        volume_id: volume.volume_id

      // call dsl.set_data() with that object as the argument and the alert
      // will now have this additional information associated with it

      // our condition check
      // is the volume.volume_type not the same as our desired type?
      if (volume.volume_type !== type_to_check_for) {

        // in this block the volume.volume_type !== type_to_check_for
        // You will create a failed alert with a message.
        // The message is a string, and the failed alert is created by calling
        // dsl.fail({ message: 'some message indicating why'})
        // You then push that object on to the alerts array and the next
        // volume is checked

        var fail_message = 'volume with id '
        fail_message += volume.volume_id + ' is of type '
        fail_message += volume.volume_type + ' and not of type '
        fail_message += type_to_check_for;

        // add the alert to the array of alerts
          message: fail_message

      } else {

        // in this block the volume.volume_type === type_to_check_for
        // You will create a pass alert with a message.

        var pass_message = 'volume with id ' + volume.volume_id
        pass_message += ' is of type ' + volume.volume_type;

        // add the alert to the array of alerts
          message: pass_message



    // return the array of alerts
    return alerts;

  } catch (err) {
    return dsl.error({
      errors: err.message

Supported Services

When calling AWS methods and classes within Custom Signatures, please use the list below as a reference.

Class Name Method Name
AutoScaling as
CloudFormation cfm
CloudFront cf
CloudSearch cs
CloudTrail ct
CloudWatch cw
CloudWatchLogs cwl
CodeDeploy cd
CognitoIdentity cognito
CognitoSync cognito_sync
ConfigService config
DataPipeline dp
DirectConnect dc
DynamoDB dynamodb
EC2 ec2
EMR emr
ElastiCache ec
ElasticBeanstalk elbs
ElasticLoadBalancing elb
ElasticTranscoder elt
Glacier glacier
IAM iam
ImportExport ie
KMS kms
Kinesis ks
Lambda lambda
OpsWorks ops
RDS rds
Redshift rs
Route53 route53
Route53Domains route53_domains
S3 s3
SES ses
SNS sns
SQS sqs
STS sts
SWF swf
SimpleDB sdb
StorageGateway sg
Support support