Skip to main content

Security report for autodesk.org

Autodesk Foundation · Technology · United States

Low risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

76/100

Risk levelLow

0–100, higher is better. How it is calculated

The Autodesk Foundation is a philanthropic entity aligned with Autodesk Inc., focusing on supporting innovative solutions to social and environmental challenges globally. It operates by providing grants, impact investments, and access to Autodesk technology and expertise to nonprofits and startups. The foundation positions itself as a key player in driving sustainable and inclusive innovation, leveraging its parent company's resources and market presence. The website reflects a mature digital presence with clear branding, comprehensive content, and strong user experience, targeting innovators and organizations focused on impact. Technically, the site employs modern web technologies, including Adobe Experience Manager CMS, Akamai CDN, and Dynatrace monitoring, ensuring good performance and accessibility. Security posture is solid with standard headers and valid SSL certificates, though some TLS protocols appear disabled, which may be a scanning artifact. Privacy and legal policies are well linked and comprehensive, supporting GDPR compliance. However, explicit security policies and incident response information are not publicly detailed, representing an area for improvement.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

6 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching autodesk.org

This scan found 14 issues across 5 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
97
Security headers
50
Email security
100
DNS health
85
Network security
100
GDPR outside view
25
Average
76

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Autodesk Foundation leverages Autodesk's brand and technology to support social impact initiatives, focusing on sectors like energy, health, and workforce development. Its business model is philanthropic, investing in early-stage innovations to scale solutions addressing climate change and inequality. The foundation's market position is strong due to its backing by a major technology company and its targeted impact areas. The website indicates a strategic approach to impact measurement and management, highlighting accountability and evidence-based investment. Partnerships with payment processors and content vendors are evident, supporting a robust operational ecosystem. The foundation's digital maturity is high, with integrated analytics and marketing tools, and a clear focus on user engagement through social media and content-rich pages.

Security posture

The website demonstrates a good security baseline with essential HTTP security headers like HSTS, X-XSS-Protection, and X-Content-Type-Options. The SSL certificate is valid and issued by a reputable CA (Amazon RSA 2048 M02). No known SSL/TLS vulnerabilities such as Heartbleed, POODLE, FREAK, or Logjam are detected. However, the absence of enabled TLS protocols in the scan suggests a potential misconfiguration or scanning anomaly that should be verified. DNSSEC and CAA records are not enabled, which could improve domain security. There is no public security policy or incident response contact information, which limits transparency and readiness perception. Cookie consent mechanisms and privacy policies are in place, supporting compliance with GDPR. Overall, the security posture is good but could be enhanced by enabling modern TLS versions, implementing DNSSEC/CAA, and publishing explicit security and incident response documentation.

Recommendations

  1. Enable TLS 1.2 and TLS 1.3 protocols to ensure secure communications and compatibility.
  2. Implement DNSSEC and CAA DNS records to strengthen domain security and certificate issuance control.
  3. Publish a dedicated security policy and incident response page with clear contact channels.
  4. Add a security.txt file at the root domain to facilitate vulnerability disclosure and communication.
  5. Regularly audit and update cookie consent mechanisms to maintain privacy compliance and transparency.
Technical notes

Notes

The website is built on Adobe Experience Manager CMS, leveraging Akamai CDN for content delivery and Amazon AWS for hosting. It uses modern JavaScript frameworks and libraries, including React-based micro frontends and Material UI components, ensuring a responsive and accessible user interface. Performance is optimized with preloading of fonts and stylesheets, lazy loading of images, and deferred script loading. Analytics and monitoring are implemented via Dynatrace and Tealium, providing comprehensive user behavior insights. The technical infrastructure is robust and scalable, supporting a large enterprise-level digital presence. Opportunities exist to modernize SSL/TLS configurations and enhance DNS security settings to reduce technical risks.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with autodesk.org. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review autodesk.org.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.