Securing applications from malicious attack
IBM Connections provides security measures, such as an active content filter and content upload limits, used to mitigate the risk of malicious attacks. Because these security measures can also limit the flexibility of the applications, you, as the system administrator, must evaluate the security of the network and determine whether or not implement them.
Any software that displays user authored content can be vulnerable to cross-site scripting (XSS) attacks. Attackers can introduce JavaScript into their content that can, among other things, steal a user's session. Session stealing in a single sign-on environment poses particular challenges because any vulnerability to XSS attacks can render the entire single sign-on domain vulnerable.
One of the ways that IBM Connections provides a defense against this type of attack is by implementing an active content filter. The active content filter removes potentially harmful text content, such as JavaScript, from user input added to a post or entry before saving the post or entry to an application; it does not filter file attachments. We can turn off the active content filter altogether if you determine the network is safe from the threat of malicious attacks. We can also change the content that is filtered per application by editing the configuration properties.
Considerations
While securing IBM Connections against malicious attacks mitigates the vulnerability to XSS attacks, it also limits what trusted users can do. For example, it removes the ability to add dynamic JavaScript content to a blog. Some areas to consider when deciding which security measures to implement are:
- Text-based fields
- When active content filtering is enabled, users cannot add certain types of content to text-based fields. The product ships with a set of active content filter configuration files which specify which types of content are allowed and which are not. The configuration files used by the product by default allow users to edit styles and add forms to entries in each of the applications. They also allow users of the Blogs and Wikis applications to add flash content to entries. We can use the default filter settings or we can choose to apply other settings. See Configure the active content filter for more details.
- File uploads
- Activities, Blogs, Files, Forums, and Wikis enable users to upload files, including Javascript and HTML. There is no way to guarantee these files will not contain malicious code for cross-site scripting attacks, and the Active Content Filter is not used when downloading this content. To mitigate the effects of malicious code, you should configure IBM Connections to download files using a separate domain. This forces the downloaded content to be executed in isolation, and prevents it from accessing data associated with an authenticated session. For more details, see Specify a separate file download domain.
- Custom templates
- Blogs supports the use of custom templates, which provide the ability for the blog owner to change the look of the blog. A custom template page is not filtered by the active content filter. Allowing custom template use introduces a XSS attack vulnerability.
- Configure the active content filter for Blogs, Wikis, and Forums
IBM Connections provides a set of active content filter (ACF) configuration files that we can apply to the Blogs, Wikis, or Forums applications to limit or widen the types of content that users can add to their blog posts, wiki pages, or forum posts.
- Configure the active content filter for Activities, Communities, and Bookmarks
IBM Connections provides a set of active content filter (ACF) configuration files that we can apply to the Activities, Communities, or Bookmarks applications to limit or widen the types of content that users can add to their entries.
- Mitigating a cross site scripting attack
If we deem that your network is secure enough to turn off the active content filter, consider using one of the configuration options described in this topic to mitigate an attack should one occur.
- Turning off active content filtering
Only turn off active content filtering if you have secured your network against cross-site scripting attacks by other means.
Parent topic:
Security
Related:
Protecting against malicious active content
Manage notification for broken links
Specify a separate file download domain
Related reference:
Communities configuration properties