{"id":18524535,"url":"https://github.com/stelligent/deep-security","last_synced_at":"2026-01-02T04:27:47.345Z","repository":{"id":145835082,"uuid":"196565908","full_name":"stelligent/deep-security","owner":"stelligent","description":"working repo for Trend Micro Deep Security lambda development","archived":false,"fork":false,"pushed_at":"2024-09-11T19:21:55.000Z","size":835,"stargazers_count":1,"open_issues_count":2,"forks_count":1,"subscribers_count":5,"default_branch":"master","last_synced_at":"2024-11-06T17:56:40.014Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/stelligent.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2019-07-12T11:14:16.000Z","updated_at":"2019-09-19T17:52:16.000Z","dependencies_parsed_at":"2023-07-16T16:46:31.684Z","dependency_job_id":null,"html_url":"https://github.com/stelligent/deep-security","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/stelligent%2Fdeep-security","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/stelligent%2Fdeep-security/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/stelligent%2Fdeep-security/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/stelligent%2Fdeep-security/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/stelligent","download_url":"https://codeload.github.com/stelligent/deep-security/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":231295560,"owners_count":18354326,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-06T17:42:21.215Z","updated_at":"2026-01-02T04:27:42.326Z","avatar_url":"https://github.com/stelligent.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"[![Build Status](https://circleci.com/gh/stelligent/deep-security.svg?style=shield)](https://circleci.com/gh/stelligent/deep-security)\n\n\n# AWS Config Rules for Deep Security\n\nA set of AWS Config Rules to help ensure that your AWS deployments are leveraging the protection of Deep Security. These rules help centralize your compliance information in one place, AWS Config.\n\n\n## Table of Contents\n\n* [Architecture](#architecture)\n* [Setup](#setup)\n* [Support](#support)\n* [Contribute](#contribute)\n\n## Setup\n\n## Create a User in Deep Security\n\nDuring execution, the AWS Lambda functions will query the Deep Security API. To do this, they require a Deep Security login with permissions.\n\nYou should set up a dedicated use account for API access. To configure the account with the minimum privileges (which reduces the risk if the credentials are exposed) required by this integration, follow the steps below.\n\n1. In Deep Security, go to *Administration* \u003e *User Manager* \u003e *Roles*. \n1. Click **New**. Create a new role with a unique, meaningful name.\n1. Under **Access Type**, select **Allow Access to web services API**.\n1. Under **Access Type**, deselect **Allow Access to Deep Security Manager User Interface**.\n1. On the **Computer Rights** tab, select either **All Computers** or **Selected Computers**, ensuring that only the greyed-out **View** right (under **Allow Users to**) is selected.\n1. On the **Policy Rights** tab, select **Selected Policies**. Verify that no policies are selected. (The role does not grant rights for any policies.)\n1. On the **User Rights** tab, select **Change own password and contact information only**.\n1. On the **Other Rights** tab, verify that the default options remain, with only **View-Only** and **Hide** permissions.\n1. Go to **Administration** \u003e **User Manager** \u003e **Users**.\n1. Click **New**. Create a new user with a unique, meaningful name.\n1. Select the role that you created in the previous section.\n\n\n### Manage secrets\n\nDeep Security Config rules utilize AWS SSM Parameter Store and KMS to securely manage credentials. Before deploying\nDeep Security Lambda functions and Config rules, you need to create entries in Parameter Store for above created\nuser's username and password. Be sure to select `SecureString` as parameter type and use appropriate KMS 'Customer managed key (CMK)' \nfrom your account. These 2 Parameter Store keys will be added as environment variables for deployment process\ndescribed below.\n\n\n### Deploy AWS Lambda and Config rules\n\nThis project is designed be deployed via several Bash scripts, but certain configuration needs to be in place fist.\n\nEnvironment variables file - `deploy.config`\n\n\u003e - `STACK_NAME`: CloudFormation stack name for all lambda and Config rule resources\n\u003e - `LAMBDA_BUCKET`: S3 bucket name where Lambda source code is uploaded\n\u003e - `LAMBDA_PREFIX`: S3 object prefix within `LAMBDA_BUCKET`\n\u003e - `CONFIG_BUCKET`: S3 bucket name where AWS Config to store history and files\n\u003e - `CONFIG_PREFIX`: S3 object prefix within `CONFIG_BUCKET`\n\u003e - `DS_HOSTNAME`: Deep Security Manager host name\n\u003e - `DS_PORT`: (optional) Deep Security Manager host port (default: 443)\n\u003e - `DS_TENANT`: (optional) Deep Security tenant name (default: '')\n\u003e - `DS_IGNORE_SSL_VALIDATION`: (optional) Whether to validate SSL connection to Deep Security Manager (default: false)\n\u003e - `DS_USERNAME_PARAM_STORE_KEY`: SSM Parameter Store key to retrieve Deep Security username\n\u003e - `DS_PASSWORD_PARAM_STORE_KEY`: SSM Parameter Store key to retrieve Deep Security password\n\u003e - `DS_POLICY`: Policy name to check used by `DoesInstanceHavePolicy` Lambda\n\u003e - `DS_CONTROL`: Control name to check used by `IsInstanceProtectedBy` Lambda (Allowed values are\n\u003e [ anti_malware, web_reputation, firewall, intrusion_prevention, integrity_monitoring, log_inspection ])\n\nDependencies\n\n- Python 3.7\n- AWS SAM CLI command line tools ([instructions](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-install.html))\n- AWS credentials correctly configured. ([instructions](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html))\n\nTo deploy\n\n`./deploy.sh`\n\nTo run unit tests\n\n`pytest -s -vv`\n\nTo publish to AWS Serverless Application Repository\n\n`./publish.sh`\n\n\n## [circleci](https://circleci.com/) Configuration\n\nThis project is managed by a CircleCI CI loop. It does require some configuration be set up to do so, though.\n\n- Create an account with `circleci` if you don't have one.\n- In `circleci`, add this project (or your copy).\n- In `project settings` of added project, `environment variables` section, add the following variables:\n\u003e   - `STACK_NAME`: CloudFormation stack name for all lambda and Config rule resources\n\u003e   - `LAMBDA_BUCKET`: S3 bucket name where Lambda source code is uploaded\n\u003e   - `LAMBDA_PREFIX`: S3 object prefix within `LAMBDA_BUCKET`\n\u003e   - `CONFIG_BUCKET`: S3 bucket name where AWS Config to store history and files\n\u003e   - `CONFIG_PREFIX`: S3 object prefix within `CONFIG_BUCKET`\n\u003e   - `DS_HOSTNAME`: Deep Security Manager host name\n\u003e   - `DS_PORT`: (optional) Deep Security Manager host port (default: 443)\n\u003e   - `DS_TENANT`: (optional) Deep Security tenant name (default: '')\n\u003e   - `DS_IGNORE_SSL_VALIDATION`: (optional) Whether to validate SSL connection to Deep Security Manager (default: false)\n\u003e   - `DS_USERNAME_PARAM_STORE_KEY`: SSM Parameter Store key to retrieve Deep Security username\n\u003e   - `DS_PASSWORD_PARAM_STORE_KEY`: SSM Parameter Store key to retrieve Deep Security password\n\u003e   - `DS_POLICY`: Policy name to check used by `DoesInstanceHavePolicy` Lambda\n\u003e   - `DS_CONTROL`: Control name to check used by `IsInstanceProtectedBy` Lambda (Allowed values are\n\u003e   [ anti_malware, web_reputation, firewall, intrusion_prevention, integrity_monitoring, log_inspection ])\n\u003e   - `AWS_ACCESS_KEY_ID`: Your AWS access key ID\n\u003e   - `AWS_SECRET_ACCESS_KEY`: Your AWS secret access key\n\u003e   - `AWS_SESSION_TOKEN`: (optional) Session token if you need one to access AWS\n\u003e   - `AWS_DEFAULT_REGION`: AWS region to deploy into\n- Done. Now when you push into your GitHub repository, `circleci` deployment will be triggered automatically.\n- **Note:** Configuration settings for `circleci` are located at `.circleci/config.yml`.\n\n### Rules\n\n#### IsInstanceProtectedByAntiMalware\n\nChecks to see if the current instance is protected by Deep Security Anti-Malware controls. Anti-malware must be \"on\" and in \"real-time\" mode for the rule to be considered compliant.\n\nLambda handler: **dsIsInstanceProtectedByAntiMalware.aws_config_rule_handler**\n\n##### Rule Parameters:\n\n\u003ctable\u003e\n\u003ctr\u003e\n  \u003cth\u003eRule Parameter\u003c/th\u003e\n  \u003cth\u003eExpected Value Type\u003c/th\u003e\n  \u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsUsernameKey\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eSSM Parameter Store key to retrive username of the Deep Security account to use for querying anti-malware status\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPasswordKey\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eSSM Parameter Store key to retrive password for the Deep Security account to use for querying anti-malware status. \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPasswordEncryptionContext\u003c/td\u003e\n  \u003ctd\u003estring or URI\u003c/td\u003e\n  \u003ctd\u003eThe encryption context used to encrypt the \u003ccode\u003edsPassword\u003c/code\u003e. If this parameter is given, the rule will include the encryption context information when decrypting the \u003ccode\u003edsPassword\u003c/code\u003e value. Requires \u003ccode\u003edsPasswordKey\u003c/code\u003e to be useful. See [Protecting Your Deep Security Manager API Password](#protecting-your-deep-security-manager-api-password) below for more details.\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsTenant\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional as long as dsHostname is specified\u003c/i\u003e. Indicates which tenant to sign in to within Deep Security\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsHostname\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional as long as dsTenant is specified\u003c/i\u003e. Defaults to Deep Security as a Service. Indicates which Deep Security manager the rule should sign in to\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPort\u003c/td\u003e\n  \u003ctd\u003eint\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional\u003c/i\u003e. Defaults to 443. Indicates the port to connect to the Deep Security manager on\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsIgnoreSslValidation\u003c/td\u003e\n  \u003ctd\u003eboolean (true or false)\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional\u003c/i\u003e. Use only when connecting to a Deep Security manager that is using a self-signed SSL certificate\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/table\u003e\n\nDuring execution, this rule sign in to the Deep Security API. You should setup a dedicated API access account to do this. Deep Security contains a robust role-based access control (RBAC) framework which you can use to ensure that this set of credentials has the least amount of privileges to success.\n\nThis rule requires view access to one or more computers within Deep Security.\n\n#### IsInstanceProtectedBy\n\nChecks to see if the current instance is protected by any of Deep Security's controls. Controls must be \"on\" and set to their strongest setting (a/k/a \"real-time\" or \"prevention\") in order for the rule to be considered compliant.\n\nThis is the generic version of *IsInstanceProtectedByAntiMalware*.\n\nLambda handler: **dsIsInstanceProtectedBy.aws_config_rule_handler**\n\n##### Rule Parameters:\n\n\u003ctable\u003e\n\u003ctr\u003e\n  \u003cth\u003eRule Parameter\u003c/th\u003e\n  \u003cth\u003eExpected Value Type\u003c/th\u003e\n  \u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsUsernameKey\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eSSM Parameter Store key to retrive username of the Deep Security account to use for querying anti-malware status\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPasswordKey\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eSSM Parameter Store key to retrive password for the Deep Security account to use for querying anti-malware status. \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPasswordEncryptionContext\u003c/td\u003e\n  \u003ctd\u003estring or URI\u003c/td\u003e\n  \u003ctd\u003eThe encryption context used to encrypt the \u003ccode\u003edsPassword\u003c/code\u003e. If this parameter is given, the rule will include the encryption context information when decrypting the \u003ccode\u003edsPassword\u003c/code\u003e value. Requires \u003ccode\u003edsPasswordKey\u003c/code\u003e to be useful. See [Protecting Your Deep Security Manager API Password](#protecting-your-deep-security-manager-api-password) below for more details.\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsTenant\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional as long as dsHostname is specified\u003c/i\u003e. Indicates which tenant to sign in to within Deep Security\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsHostname\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional as long as dsTenant is specified\u003c/i\u003e. Defaults to Deep Security as a Service. Indicates which Deep Security manager the rule should sign in to\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPort\u003c/td\u003e\n  \u003ctd\u003eint\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional\u003c/i\u003e. Defaults to 443. Indicates the port to connect to the Deep Security manager on\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsIgnoreSslValidation\u003c/td\u003e\n  \u003ctd\u003eboolean (true or false)\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional\u003c/i\u003e. Use only when connecting to a Deep Security manager that is using a self-signed SSL certificate\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsControl\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eThe name of the control to verify. Must be one of [ anti_malware, web_reputation, firewall, intrusion_prevention, integrity_monitoring, log_inspection ]\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/table\u003e\n\nDuring execution, this rule signs in to the Deep Security API. You should setup a dedicated API access account to do this. Deep Security contains a robust role-based access control (RBAC) framework which you can use to ensure that this set of credentials has the least amount of privileges to success.\n\nThis rule requires view access to one or more computers within Deep Security.\n\n#### DoesInstanceHavePolicy\n\nChecks to see if the current instance is protected by a specific Deep Security policy.\n\nLambda handler: **dsDoesInstanceHavePolicy.aws_config_rule_handler**\n\n##### Rule Parameters:\n\n\u003ctable\u003e\n\u003ctr\u003e\n  \u003cth\u003eRule Parameter\u003c/th\u003e\n  \u003cth\u003eExpected Value Type\u003c/th\u003e\n  \u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsUsernameKey\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eSSM Parameter Store key to retrive username of the Deep Security account to use for querying anti-malware status\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPasswordKey\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eSSM Parameter Store key to retrive password for the Deep Security account to use for querying anti-malware status. \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPasswordEncryptionContext\u003c/td\u003e\n  \u003ctd\u003estring or URI\u003c/td\u003e\n  \u003ctd\u003eThe encryption context used to encrypt the \u003ccode\u003edsPassword\u003c/code\u003e. If this parameter is given, the rule will include the encryption context information when decrypting the \u003ccode\u003edsPassword\u003c/code\u003e value. Requires \u003ccode\u003edsPasswordKey\u003c/code\u003e to be useful. See [Protecting Your Deep Security Manager API Password](#protecting-your-deep-security-manager-api-password) below for more details.\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsTenant\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional as long as dsHostname is specified\u003c/i\u003e. Indicates which tenant to sign in to within Deep Security\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsHostname\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional as long as dsTenant is specified\u003c/i\u003e. Defaults to Deep Security as a Service. Indicates which Deep Security manager the rule should sign in to\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPort\u003c/td\u003e\n  \u003ctd\u003eint\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional\u003c/i\u003e. Defaults to 443. Indicates the port to connect to the Deep Security manager on\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsIgnoreSslValidation\u003c/td\u003e\n  \u003ctd\u003eboolean (true or false)\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional\u003c/i\u003e. Use only when connecting to a Deep Security manager that is using a self-signed SSL certificate\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPolicy\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eThe name of the policy to verify\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/table\u003e\n\nDuring execution, this rule signs in to the Deep Security API. You should setup a dedicated API access account to do this. Deep Security contains a robust role-based access control (RBAC) framework which you can use to ensure that this set of credentials has the least amount of privileges to success.\n\nThis rule requires view access to one or more computers within Deep Security.\n\n#### IsInstanceClear\n\nChecks to see if the current instance is has any warnings, alerts, or errors in Deep Security. An instance is compliant if it does **not** have any warnings, alerts, or errors (a/k/a compliant, which means everything is working as expected with no active security alerts).\n\nLambda handler: **dsIsInstanceClear.aws_config_rule_handler**\n\n##### Rule Parameters:\n\n\u003ctable\u003e\n\u003ctr\u003e\n  \u003cth\u003eRule Parameter\u003c/th\u003e\n  \u003cth\u003eExpected Value Type\u003c/th\u003e\n  \u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsUsernameKey\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eSSM Parameter Store key to retrive username of the Deep Security account to use for querying anti-malware status\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPasswordKey\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003eSSM Parameter Store key to retrive password for the Deep Security account to use for querying anti-malware status. \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPasswordEncryptionContext\u003c/td\u003e\n  \u003ctd\u003estring or URI\u003c/td\u003e\n  \u003ctd\u003eThe encryption context used to encrypt the \u003ccode\u003edsPassword\u003c/code\u003e. If this parameter is given, the rule will include the encryption context information when decrypting the \u003ccode\u003edsPassword\u003c/code\u003e value. Requires \u003ccode\u003edsPasswordKey\u003c/code\u003e to be useful. See [Protecting Your Deep Security Manager API Password](#protecting-your-deep-security-manager-api-password) below for more details.\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsTenant\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional as long as dsHostname is specified\u003c/i\u003e. Indicates which tenant to sign in to within Deep Security\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsHostname\u003c/td\u003e\n  \u003ctd\u003estring\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional as long as dsTenant is specified\u003c/i\u003e. Defaults to Deep Security as a Service. Indicates which Deep Security manager the rule should sign in to\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsPort\u003c/td\u003e\n  \u003ctd\u003eint\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional\u003c/i\u003e. Defaults to 443. Indicates the port to connect to the Deep Security manager on\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n  \u003ctd\u003edsIgnoreSslValidation\u003c/td\u003e\n  \u003ctd\u003eboolean (true or false)\u003c/td\u003e\n  \u003ctd\u003e\u003ci\u003eOptional\u003c/i\u003e. Use only when connecting to a Deep Security manager that is using a self-signed SSL certificate\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/table\u003e\n\nDuring execution, this rule signs in to the Deep Security API. You should setup a dedicated API access account to do this. Deep Security contains a robust role-based access control (RBAC) framework which you can use to ensure that this set of credentials has the least amount of privileges to success.\n\nThis rule requires view access to one or more computers within Deep Security.\n\n## Support\n\nThis is an Open Source community project. Project contributors may be able to help, \ndepending on their time and availability. Please be specific about what you're \ntrying to do, your system, and steps to reproduce the problem.\n\nFor bug reports or feature requests, please \n[open an issue](../issues). \nYou are welcome to [contribute](#contribute).\n\nOfficial support from Trend Micro is not available. Individual contributors may be \nTrend Micro employees, but are not official support.\n\n## Contribute\n\nWe accept contributions from the community. To submit changes:\n\n1. Fork this repository.\n1. Create a new feature branch.\n1. Make your changes.\n1. Submit a pull request with an explanation of your changes or additions.\n\nWe will review and work with you to release the code.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fstelligent%2Fdeep-security","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fstelligent%2Fdeep-security","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fstelligent%2Fdeep-security/lists"}