Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

RSS

deep-security-agent (11) Versions 1.1.1

Installs/Configures the Deep Security Agent

Berkshelf
Policyfile
Knife
cookbook 'deep-security-agent', '= 1.1.1'
cookbook 'deep-security-agent', '= 1.1.1', :supermarket
knife cookbook site install deep-security-agent
knife cookbook site download deep-security-agent
README
Dependencies
Changelog
Quality 44%

A collection of recipes to help deploy and manage the Trend Micro Deep Security Agent.

Requirements

All of the recipes in this cookbook require a working Deep Security infrastructure. The key component is the Trend Micro Deep Security Manager. The agents (which these recipes help you manage) do the heavy lifting but the manager gives the marching orders.

There are no specific technical requirements beyond a standard Chef deployment.

Attributes

Recipe : deep-security-agent::default

The "default" recipe runs the "deep-security-agent::dsa-install" and "deep-security-agent::dsa-activate" recipes internally.

Key Type Description Default
['dsm_agent_download_hostname'] String Hostname of the Deep Security Manager. app.deepsecurity.trendmicro.com
['dsm_agent_download_port'] Int The port to connect to the Deep Security Manager to download the agents. This is typically the same port as the one used to access the Deep Security Manager admin interface. 443
['ignore_ssl_validation'] Boolean Whether or not to ignore the SSL certificate validation for agent downloads. Marketplace and software deployments ship with self-signed certificates and require this set to 'true'. false
['dsm_agent_activation_hostname'] String The hostname for the agents to communicate with once deployed. For Marketplace and software deployments this is typically the same hostname as 'dsm_agent_download_hostname'. agents.deepsecurity.trendmicro.com
['dsm_agent_activation_port'] Int The port to use for the agent heartbeat (the regular communication). For Marketplace and software deployments, the default is 4120. 443
['tenant_id'] String In a multi-tenant installation (like Deep Security as a Service), this identifies the tenant account to register the agent with. nil
['token'] String In a multi-tenant installation (like Trend Micro Deep Security as a Service), this identifies the tenant account to register the agent with. nil
['policy_id'] String The Deep Security ID assigned to the policy to apply to the agents on activation. nil
['force_reactivation'] Boolean Whether to force re-activation even Deep Security Agent has been activated. false

Recipe : deep-security-agent::dsa-install

"dsa-install" recipe will download and install the Deep Security Agent service. Installation will be skipped if agent with same version already installed. If downloaded Deep Security Installer version is newer, then version upgrade will be performed.

Key Type Description Default
['dsm_agent_download_hostname'] String Hostname of the Deep Security Manager. app.deepsecurity.trendmicro.com
['dsm_agent_download_port'] Int The port to connect to the Deep Security Manager to download the agents. This is typically the same port as the one used to access the Deep Security Manager admin interface. 443
['ignore_ssl_validation'] Boolean Whether or not to ignore the SSL certificate validation for agent downloads. Marketplace and software deployments ship with self-signed certificates and require this set to 'true'. false

Recipe : deep-security-agent::dsa-activate

"dsa-activate" recipe will activate the Deep Security Agent service by registering into Trend Micro Deep Security Manager. By default, this recipe will skip activation if agent already in activated state, unless 'force_reactivation' attribute is set to 'true'.

Key Type Description Default
['dsm_agent_activation_hostname'] String The hostname for the agents to communicate with once deployed. For Marketplace and software deployments this is typically the same hostname as 'dsm_agent_download_hostname'. agents.deepsecurity.trendmicro.com
['dsm_agent_activation_port'] Int The port to use for the agent heartbeat (the regular communication). For Marketplace and software deployments, the default is 4120. 443
['tenant_id'] String In a multi-tenant installation (like Deep Security as a Service), this identifies the tenant account to register the agent with. nil
['token'] String In a multi-tenant installation (like Trend Micro Deep Security as a Service), this identifies the tenant account to register the agent with. nil
['policy_id'] String The Deep Security ID assigned to the policy to apply to the agents on activation. nil
['force_reactivation'] Boolean Whether to force re-activation even Deep Security Agent has been activated. false

Usage

Recipe : deep-security-agent::default

Make sure that you include 'deep-security-agent' in your node's 'run_list'. This ensures that the Deep Security Agent is installed (it's the default.rb recipe).

{
  "name":"my_node",
  "default_attributes": {
    "deep_security_agent" : {
      "dsm_agent_download_hostname": "app.deepsecurity.trendmicro.com",
      "dsm_agent_download_port" : "443",
      "dsm_agent_activation_hostname" : "agents.deepsecurity.trendmicro.com",
      "dsm_agent_activation_port" : "443",
      "tenant_id" : "<Deep Security DSAAS Tenant ID>",
      "token" : "<Deep Security DSAAS Tenant Token>"
    }
  },
  "run_list": [
    "recipe[deep-security-agent::default]"
  ]
}

Acknowledgment

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Change Log

Please refer to GitHub Deep-Security-Agent cookbook releases for complete change log.

Collaborator Number Metric
            

1.1.1 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

1.1.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

1.1.1 failed this metric

FC064: Ensure issues_url is set in metadata: deep-security-agent/metadata.rb:1
FC065: Ensure source_url is set in metadata: deep-security-agent/metadata.rb:1
FC066: Ensure chef_version is set in metadata: deep-security-agent/metadata.rb:1
Run with Foodcritic Version 12.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

1.1.1 failed this metric

deep-security-agent does not have a valid open source license.
Acceptable licenses include Apache-2.0, apachev2, Apache 2.0, MIT, mit, GPL-2.0, gplv2, GNU Public License 2.0, GPL-3.0, gplv3, GNU Public License 3.0.

No Binaries Metric
            

1.1.1 passed this metric

Publish Metric
            

1.1.1 passed this metric

Supported Platforms Metric
            

1.1.1 passed this metric

Testing File Metric
            

1.1.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

1.1.1 passed this metric