SSL directory permissions guidelines
Security
- Agent authentication
- Bamboo cookies
- Best practices for Bamboo security
- Securing Bamboo against potential SSRF attacks
- Securing your remote agents
- Serialization protection methods
- Configuring XSRF protection
- Managing trusted keys
- System-wide encryption
- Repository-stored Bamboo Specs security
- Securing a database password
- Encrypting passwords in server.xml
- Requiring personal access token expiration
- Configuring the allowlist
- SSL directory permissions guidelines
- Configure secure administrator sessions (websudo)
- Log escaping and security enhancements
On this page
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
Since Bamboo 9.6, application nodes use gRPC for the inter-node commutation. To ensure secure data exchange, the gRPC layer uses mTLS for which certificates and keys are laying in the `<bamboo-shared-home>/ssl.` To enhance the security, we recommend the `SSL` directory should have manually restricted access.
The directory and all its content should be accessible only by authorized users/services, specifically the ones running the application nodes, to allow nodes free read/write/execute access. No other users or services should have access to this directory.
Last modified on Nov 28, 2024
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
Powered by Confluence and Scroll Viewport.