# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Palo Alto Networks Prisma Cloud DSPM Risks API
  version: 1.0.0
extends: openapi/palo-alto-networks-risks-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 3
- target: $.paths['/dspm/api/v1/risks'].get
  update:
    x-apievangelist-phrasing:
      intent: List data security risks
      effect: read
      questions:
      - Which data stores have sensitive data exposed by insecure configurations?
      - Can I filter data risks by risk level, status or cloud provider?
      - What are my highest-severity open data security risks?
      instructions:
      - text: List all data security risks.
      - text: List {riskLevel} risks with status {status}.
        slots:
          riskLevel: query.riskLevel
          status: query.status
      - text: Show data risks in cloud provider {cloudProvider} sorted by {sortBy}.
        slots:
          cloudProvider: query.cloudProvider
          sortBy: query.sortBy
      method: generated
      generated: '2026-09-26'
- target: $.paths['/dspm/api/v1/risks/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get details and remediation for a data risk
      effect: read
      questions:
      - What remediation steps are recommended for a specific data risk?
      - Which data assets are impacted by one particular risk?
      instructions:
      - text: Get data risk {id}.
        slots:
          id: path.id
      - text: Show the remediation guidance for risk {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/dspm/api/v1/risks/{id}/status'].put
  update:
    x-apievangelist-phrasing:
      intent: Change a data risk's status
      effect: write
      questions:
      - How do I mark a data risk as remediated after fixing the data store?
      - Can I suppress or acknowledge a risk with a comment?
      instructions:
      - text: Set risk {id} status to {status}.
        slots:
          id: path.id
          status: requestBody.status
      - text: Mark risk {id} as {status} with comment {comment}.
        slots:
          id: path.id
          status: requestBody.status
          comment: requestBody.comment
      method: generated
      generated: '2026-09-26'