@newrelic/security-agent

New Relic Node.js security agent

Note: The IAST capability should only be used in pre-production environments as the application is tested for real exploitable vulnerabilities.

The New Relic security agent enables instrumentation of a Node.js application for Interactive Application Security Testing(IAST) and exposes exploitable vulnerabilities.

Installation

Typically, most users use the version auto-installed by the New Relic Node.js agent. You can see agent install instructions here.

In some cases, installing a specific version is ideal. For example, new features or major changes might be released via a major version update to this module, prior to inclusion in the main New Relic Node.js Agent.

npm install @newrelic/security-agent@latest

For more information, please see New Relic Node.js agent installation guide

The @newrelic/security-agent must be explicitly enabled in order to perform IAST analysis of the application. In the newrelic.js, set the following parameters

 /**
  * Security Configurations
  */
   security: {
    /**
     * enables/disables security agent functions and generation of events.
     */
    enabled: true,
    /**
      * To completely disable security, set agent.enabled flag to false. If the flag is set to false, the security module is not loaded. This property is read only once at application start.
      */
    agent: {
      enabled: true
    }
  }

Getting Started

The Developer docs for writing instrumentation will be of help. We particularly recommend the tutorials and the shim API documentation.

Supported Node.js Versions

• Node version 18.x, 20.x and 22.x

Supported Modules

• Node.js core modules
  • http
  • https
  • fs
  • child_process
• mysql(2.16.x and above)
• mysql2 (2.x and above)
• pg(7.x and above)
• mongodb(2.x, 3.x and 4.x)
• express(4.x and above)
• @koa/router (9.x and above)
• koa-router(9.x and above)
• @hapi/hapi(19.x and above)
• fastify(2.x, 3.x and 4.x)
• restify(8.x, 9.x, 10.x and 11.x)
• director(1.2.x)
• @nestjs/core(8.x and above)
• ldapjs(2.x and above)
• ldapts(2.x and above)
• xpath(0.0.20 and above)
• xpath.js(0.0.1 and above)
• undici(4.7.0 and above)

For more information, please see New Relic Node.js agent compatibility and requirements.

Supported Vulnerabilities

• Remote Code Execution
• SQL Injection
• NoSQL Injection
• Stored XSS
• Reflected XSS
• Reverse Shell attack
• File Access
• SSRF
• Application Integrity Violation
• LDAP Injection
• XPath Injection

Testing

The module includes a suite of unit and functional tests which should be used to verify that your changes don't break existing functionality.

All tests are stored in tests/ and are written using Tap with the extension .tap.js.

To run the full suite, run: npm test.

Support

New Relic hosts and moderates an online forum where you can interact with New Relic employees as well as other customers to get help and share best practices. You can find this project's topic/threads here: Add the url for the support thread here: https://forum.newrelic.com/s/

Contribute

Any feedback provided to New Relic about the New Relic security agent, including feedback provided as source code, comments, or other copyrightable or patentable material, is provided to New Relic under the terms of the New Relic Software License v1.0. If you do not provide attribution information or a copy of the license with your feedback, you waive the performance of those requirements of the New Relic Software License v1.0 with respect to New Relic. The license grant regarding any feedback is irrevocable. Keep in mind that when you submit a pull request or other feedback, you’ll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. If you have any questions drop us an email at [e-mail].

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

If you would like to contribute to this project, review these guidelines.

License

The New Relic security agent is licensed under the New Relic Software License v1.0. The @newrelic/security-agent also uses source code from third-party libraries. You can find full details on which libraries are used and the terms under which they are licensed in the third-party notices document.

Changelog

v2.1.1 (2024-11-07)

Bug fixes

• Fix for assignment to logger constant