Generated SDK #2791732002 (major) - #157
Conversation
|
Thanks for submitting this request. We'll review it and provide updates soon. (Note that this SDK code is auto generated) |
![semgrep-code-fireblocks[bot]](https://avatars.githubusercontent.com/u/40918269?s=60&v=4){kind=small}
| category = 'USER_MANAGEMENT', | ||
| created_at = '2026-07-28T11:37:05Z', | ||
| title = 'The API user 'Security admin api' is paired with a co-signer and has no callback', | ||
| info = {"apiKey":"e7c3f18c-3060-3748-3563-19c3dbb3fa88","apiUserName":"Security admin api","cosignerId":"02f53cfa-34a3-4393-a451-e13dfab3c157","cosignerName":"Production Co-Signer"}, |
There was a problem hiding this comment.
Hardcoded sensitive data leaked
Semgrep has detected a leak of sensitive data in this code. This secret data could be used by internal or external malicious actors. We highly recommend you change, reset, or rotate the sensitive data.
A secret is hard-coded in the application. Secrets stored in source code, such as credentials, identifiers, and other types of sensitive data, can be leaked and used by internal or external malicious actors. It is recommended to rotate the secret and retrieve them from a secure secret vault or Hardware Security Module (HSM), alternatively environment variables can be used if allowed by your company policy.
💬 To ignore this, reply with:
• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons
Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by string.
| status_updated_at = '2026-08-16T08:52:57Z', | ||
| status_updated_by_user_id = '00d77437-3e7a-4e39-8482-55115a7a0892', | ||
| status_updated_reason = 'False positive, callback is configured via a different mechanism', | ||
| info = {"apiKey":"e7c3f18c-3060-3748-3563-19c3dbb3fa88","apiUserName":"Security admin api","cosignerId":"02f53cfa-34a3-4393-a451-e13dfab3c157","cosignerName":"Production Co-Signer"}, |
There was a problem hiding this comment.
Hardcoded sensitive data leaked
Semgrep has detected a leak of sensitive data in this code. This secret data could be used by internal or external malicious actors. We highly recommend you change, reset, or rotate the sensitive data.
A secret is hard-coded in the application. Secrets stored in source code, such as credentials, identifiers, and other types of sensitive data, can be leaked and used by internal or external malicious actors. It is recommended to rotate the secret and retrieve them from a secure secret vault or Hardware Security Module (HSM), alternatively environment variables can be used if allowed by your company policy.
💬 To ignore this, reply with:
• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons
Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by string.
2 participants
Changelog
2026-08-26
Breaking Change
Remove deprecated FSPM category filter values
Products: Security Posture Management
Scope: API + SDKs
What's new
Removes ACCESS_CONTROL, ADMIN_MANAGEMENT, SECURITY, and CONFIGURATION values from the category filter parameter and updates the endpoint description text.
Impact
API requests using the removed category filter values will receive validation errors.
Affected endpoints:
Added
Add FSPM security finding update endpoint
Products: Security Posture Management
Scope: API + SDKs
What's new
Adds an endpoint to accept or reopen FSPM security findings by setting the status to ACCEPTED or OPEN, with a required reason when accepting.
Impact
Customers can programmatically manage FSPM finding statuses through the API.
Affected endpoints:
Add FSPM security finding details endpoint
Products: Security Posture Management
Scope: API + SDKs
What's new
Adds an endpoint to retrieve detailed information about a specific FSPM security finding by its ID, including compliance requirements, risk explanation, and mitigation guidance.
Impact
Customers can now fetch complete details for individual security findings programmatically.
Affected endpoints: