Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NR-306872: IAST support for CI/CD #326

Merged
merged 8 commits into from
Sep 12, 2024

Conversation

IshikaDawda
Copy link
Contributor

@IshikaDawda IshikaDawda commented Aug 28, 2024

  • Honour new config security.iast_test_identifier
  • Add test identifier header in web socket headers, with header name NR-CSEC-IAST-TEST-IDENTIFIER
  • Add process start time header in web socket headers, with header name NR-CSEC-PROCESS-START-TIME

Mandatory Fields: The following fields are required to ensure accurate state tracking:

  • Process Start Time (procStartTime): The timestamp when the application or process started.
  • Traffic Start Time (trafficStartedTime): The time at which the CSEC agent recorded the first event.
  • Scan Start Time (scanStartTime): The timestamp when the first control command (fuzz request) is processed at the SA.

Optional Fields: The following fields provide additional context and can be used to gain a deeper understanding of the application's state:

  • Control Command Request Time (controlCommandRequestedTime): The timestamp of the first control command for fuzz request. This will never change.
  • CSEC Activation Time (csecActivationTime): The timestamp when the CSEC agent will activate or activated.
  • IAST Activation Time (iastDataRequestTime): The timestamp when the IAST Scan will start or started requesting control commands. (This is the time when IAST will send it’s first Data Pull Request for the particular scan window)
  • Scan Active (scanActive): A boolean indicating whether the agent is actively scanning (IAST pull request are active) (Note: This field has no relation with scan end time).

@IshikaDawda IshikaDawda self-assigned this Aug 28, 2024
@IshikaDawda IshikaDawda changed the base branch from main to feature/iast-skip-n-schedule August 30, 2024 05:08
…i-cd-support

# Conflicts:
#	newrelic-security-agent/src/main/java/com/newrelic/agent/security/AgentConfig.java
#	newrelic-security-agent/src/main/java/com/newrelic/agent/security/intcodeagent/websocket/WSClient.java
@IshikaDawda IshikaDawda changed the base branch from feature/iast-skip-n-schedule to feature/iast-scan-rate-limit August 30, 2024 05:34
@IshikaDawda IshikaDawda merged commit 99f3406 into feature/iast-scan-rate-limit Sep 12, 2024
10 checks passed
@IshikaDawda IshikaDawda deleted the feature/ci-cd-support branch September 12, 2024 05:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants