Skip to main content
Security Recommendation: iFrames

This article will outline the key risks associated with iFrames and explain why we don't recommend using them in ClearPoint.

Dylan Miyake avatar
Written by Dylan Miyake
Updated over a week ago

At ClearPoint Strategy, we aim to provide a secure and reliable platform for your reporting needs. While iFrames may seem like a convenient solution for embedding external content into your ClearPoint dashboard, they come with several security risks and compatibility issues that make them a less-than-ideal choice. This article will outline the key risks associated with iFrames and explain why we don't recommend using them in ClearPoint.

Security Risks Associated with iFrames

  1. Cross-Site Scripting (XSS) Attacks

    • iFrames can be used as an entry point for malicious scripts through cross-site scripting attacks. If the source of the iFrame is compromised or if an attacker manages to inject malicious code into the content, it could gain access to sensitive information within your ClearPoint account. XSS vulnerabilities are a significant security concern, and they can affect both users and systems by exposing them to unauthorized actions or data breaches.

  2. Clickjacking

    • An iFrame can be manipulated for "clickjacking," where an attacker overlays or hides malicious content beneath legitimate buttons or elements. Users think they are clicking something harmless, but they may be performing unintended actions, like changing settings or submitting sensitive data.

  3. Insecure Content

    • If you embed content from insecure sources (e.g., HTTP websites instead of HTTPS), you expose your ClearPoint environment to potential vulnerabilities. Modern browsers increasingly block insecure content, making iFrames not only a security concern but also likely to cause display issues.

Compatibility Issues with iFrames

  1. Browser Compatibility

    • Different browsers implement iFrame rendering in slightly different ways, and browser updates can lead to changes in how iFrames are handled. What works today might break tomorrow after a browser update. Additionally, not all browsers support the same features, which can lead to inconsistent display or functionality across platforms.

  2. Security Standards

    • As web security standards evolve, restrictions on iFrames continue to increase. For example, many websites implement Content Security Policy (CSP) headers that prevent their content from being embedded in iFrames. As more websites adopt stricter security policies, embedding third-party content via iFrames becomes increasingly unreliable.

  3. Content Restrictions

    • Some websites prevent their content from being displayed in iFrames altogether, often by using an "X-Frame-Options" header. If the site you’re trying to embed uses this security measure, the iFrame will not display the content, causing your dashboard or report to appear broken or incomplete.

  4. Third-Party Source Issues

    • Even if the iFrame source is secure and functioning today, changes to the third-party website or application can cause the iFrame to break. A simple design update, URL structure change, or security enhancement on the third-party site could disrupt the embedded content in ClearPoint.

ClearPoint Platform Changes

  1. Platform Updates

    • ClearPoint regularly updates its platform to improve security, performance, and functionality. These updates could change how iFrames are handled, potentially breaking previously embedded content. We prioritize the security of our users, and future updates may introduce tighter security controls that further restrict or disable iFrame embedding.

  2. Deprecation of iFrame Support

    • To maintain a secure environment, ClearPoint may phase out or reduce support for iFrames in favor of more secure, modern alternatives. This is in line with industry trends where security-conscious platforms minimize the use of iFrames to avoid vulnerabilities.

Recommended Alternatives

Instead of relying on iFrames, we recommend the following alternatives:

  • Direct Data Integrations: ClearPoint supports various data integration options that securely bring external data into your reporting environment without the need for embedding.

  • Linking to External Resources: If you need to reference external content, consider providing a secure hyperlink instead of embedding the content directly.

  • Embedding Secure Widgets: Some third-party services provide embeddable widgets that are specifically designed with modern security protocols. Ensure any content you embed follows industry security standards, like HTTPS and content security policies.

Conclusion

Although iFrames offer a quick and easy way to embed content, they come with significant security risks and compatibility challenges. As both ClearPoint and the broader web ecosystem continue to prioritize security, we strongly recommend exploring alternative methods for integrating external content into your ClearPoint Strategy dashboards. Avoiding iFrames helps keep your data secure and ensures long-term compatibility with web standards and ClearPoint’s evolving platform.

If you have any questions or need help exploring alternative embedding solutions, please contact our support team for assistance.

Did this answer your question?