Skip to content

feat(appsec): enable api security #636

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

florentinl
Copy link
Contributor

@florentinl florentinl commented Jul 23, 2025

What does this PR do?

This PR adds the necessary functionalities to implement API Security:

  • report the http.route tag on the entry span:
    • that means adding it to the inferred span when there is one
  • send the response body to Appsec to extract the schema of the API

Motivation

The objective of this PR is to enable API Security inside the tracer for python in lambda.

Testing Guidelines

Updated the test cases for the asm_start_response function to ensure that the body is sent to Appsec.

Updated the snapshot tests to ensure that http.route is present on required spans.

Additional Notes

This PR depends on DataDog/dd-trace-py#14118.

Types of Changes

  • Bug fix
  • New feature
  • Breaking change
  • Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

  • This PR's description is comprehensive
  • This PR contains breaking changes that are documented in the description
  • This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
  • This PR impacts documentation, and it has been updated (or a ticket has been logged)
  • This PR's changes are covered by the automated tests
  • This PR collects user input/sensitive content into Datadog
  • This PR passes the integration tests (ask a Datadog member to run the tests)

@florentinl florentinl force-pushed the florentinl/APPSEC-58369/report-route-on-inferred-span branch 3 times, most recently from abcfe53 to 0f15cf0 Compare July 24, 2025 07:53
@florentinl florentinl marked this pull request as ready for review July 24, 2025 08:33
@florentinl florentinl requested review from a team as code owners July 24, 2025 08:33
florentinl added a commit to DataDog/dd-trace-py that referenced this pull request Jul 24, 2025
## Description

Add a handler for lambda to send a response body to parse.

Additionally fix one typo

## Additional Notes

This is enabled in datadog_lambda by this PR:
DataDog/datadog-lambda-python#636

## Checklist
- [x] PR author has checked that all the criteria below are met
- The PR description includes an overview of the change
- The PR description articulates the motivation for the change
- The change includes tests OR the PR description describes a testing
strategy
- The PR description notes risks associated with the change, if any
- Newly-added code is easy to change
- The change follows the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
- The change includes or references documentation updates if necessary
- Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist
- [x] Reviewer has checked that all the criteria below are met 
- Title is accurate
- All changes are related to the pull request's stated goal
- Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- Testing strategy adequately addresses listed risks
- Newly-added code is easy to change
- Release note makes sense to a user of the library
- If necessary, author has acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment
- Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
@florentinl florentinl force-pushed the florentinl/APPSEC-58369/report-route-on-inferred-span branch from 0f15cf0 to baadddd Compare July 24, 2025 09:22
@florentinl florentinl force-pushed the florentinl/APPSEC-58369/report-route-on-inferred-span branch from baadddd to 2868513 Compare July 25, 2025 07:58
alyshawang pushed a commit to DataDog/dd-trace-py that referenced this pull request Jul 25, 2025
## Description

Add a handler for lambda to send a response body to parse.

Additionally fix one typo

## Additional Notes

This is enabled in datadog_lambda by this PR:
DataDog/datadog-lambda-python#636

## Checklist
- [x] PR author has checked that all the criteria below are met
- The PR description includes an overview of the change
- The PR description articulates the motivation for the change
- The change includes tests OR the PR description describes a testing
strategy
- The PR description notes risks associated with the change, if any
- Newly-added code is easy to change
- The change follows the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
- The change includes or references documentation updates if necessary
- Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist
- [x] Reviewer has checked that all the criteria below are met 
- Title is accurate
- All changes are related to the pull request's stated goal
- Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- Testing strategy adequately addresses listed risks
- Newly-added code is easy to change
- Release note makes sense to a user of the library
- If necessary, author has acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment
- Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
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