Skip to content

Commit d540fb3

Browse files
kumargunatebower
andauthored
Update _posts/2025-05-19-journey-to-find-replacements-java-security-manager.md
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Gulshan <[email protected]>
1 parent 380e87b commit d540fb3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2025-05-19-journey-to-find-replacements-java-security-manager.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ We specifically chose to avoid over-instrumentation because of performance and m
128128

129129
## Final thoughts
130130

131-
JSM deprecation is a significant turning point for the Java ecosystem and OpenSearch alike. While no single solution can fully replicate the functionality that JSM provided, OpenSearch's two-pronged approach---using operating-system-level protections through systemd and introducing a lightweight Java agent for plugin-level access control---provides a robust and extensible foundation for securing the platform going forward.
131+
JSM deprecation is a significant turning point for the Java ecosystem and OpenSearch alike. While no single solution can fully replicate the functionality that JSM provided, OpenSearch's two-pronged approach---using operating-system-level protections through `systemd` and introducing a lightweight Java agent for plugin-level access control---provides a robust and extensible foundation for securing the platform.
132132

133133
This approach ensures that OpenSearch remains secure, performant, and compatible with the evolving Java ecosystem while retaining the extensibility and plugin ecosystem that users rely on.
134134

0 commit comments

Comments
 (0)