Neodym Platform Security Config and SDK Fixes Update

Vulnerability Overview UI Component: - The RBAC role form now explains "unlimited visibility" in the visibility section and retains the visibility setting when the hidden group selection is changed. - The CIS Level 1 and Level 2 compliance filters now match profiles with license prefixes (e.g., "E3 Level 1"), so M365 CIS requirements are no longer hidden. - Jira polling now reports failed issue creation tasks instead of treating partial failures as successful. API Component: - Session tokens are rejected after account password updates. - Jira scheduled task results now publicly display Jira failure messages. - The AWS attack path privilege escalation query no longer fails on Neodym. Security Component: - The base URL for the OpenAI-compatible Lighthouse provider is restricted before the connection check. - The environment variable is used to allow internal hosts as OpenAI-compatible Lighthouse AI backend URLs. SDK Component: - ECS task definition resource limits now select the latest task definition based on the registration date, rather than relying on ARN sorting. - no longer initializes a full EC2 inventory to detect EBS snapshots, avoiding slow scans when checking DLM lifecycle policies. - no longer initializes the full EC2 service when there are no DMS replication instances. - no longer reports false negatives for AWS organizations that use Allow-based SCPs to restrict regions. The access path now checks statement effects instead of performing constant false comparisons, making them unreachable. - Jira issue creation failures now retain security structured response details from Jira. - Azure Function App optional permission failures are now logged as warnings, and the Function App environment variable fields use the correct spelling internally. Impact Scope UI Component: - Affects visibility settings for RBAC role forms. - Affects matching for CIS Level 1 and Level 2 compliance filters. - Affects reporting of task creation tasks in Jira polling. API Component: - Affects session token management after account password updates. - Affects the display of error messages in Jira scheduled task results. - Affects the performance of AWS attack path privilege escalation queries on Neodym. Security Component: - Affects the restriction of the base URL for the OpenAI-compatible Lighthouse provider. - Affects the usage of the environment variable. SDK Component: - Affects the selection method for ECS task definition resource limits. - Affects the initialization behavior of and . - Affects the false negative reporting of . - Affects the retention of response details for Jira issue creation failures. - Affects logging and variable field spelling for Azure Function App optional permission failures. Remediation UI Component: - Update the visibility setting logic for RBAC role forms. - Adjust matching rules for CIS Level 1 and Level 2 compliance filters. - Improve the task creation task reporting mechanism in Jira polling. API Component: - Implement a mechanism to reject session tokens after account password updates. - Publicly expose error messages for Jira scheduled task results. - Fix the issue with AWS attack path privilege escalation queries on Neodym. Security Component: - Restrict the base URL for the OpenAI-compatible Lighthouse provider. - Use the environment variable to allow internal hosts. SDK Component: - Select the latest ECS task definition based on the registration date. - Optimize the initialization behavior of and . - Correct the false negative reporting of . - Retain security structured response details for Jira issue creation failures. - Correct logging and variable field spelling for Azure Function App optional permission failures. POC Code or Exploit Code No POC code or exploit code is included in the page.

Goal Reached Thanks to every supporter — we hit 100%!

Neodym Platform Security Config and SDK Fixes Update

More from this source