Skip to main content

Security report for orchestrabrasil.com.br

Orchestra Brasil · Manufacturing · Brazil

High risk. 9 critical or high findings in Network security, Security headers and 1 other check.

Security score

49/100

Risk levelHigh

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

Orchestra Brasil is a Brazilian project focused on promoting and supporting the internationalization of suppliers in the furniture manufacturing industry. It acts as a bridge between Brazilian suppliers and global markets, facilitating export activities and participation in major international trade fairs. The project is well-established with over a decade of experience and supports nearly 100 qualified Brazilian companies exporting to more than 90 countries. The website serves importers, manufacturers, distributors, and retailers in the furniture sector, providing information and contact channels to engage with Brazilian suppliers. Technically, the website is built on WordPress and leverages common plugins such as Contact Form 7, Yoast SEO, and GDPR compliance tools. It uses Google Analytics and Facebook Pixel for tracking and marketing automation via Mautic. The hosting provider is KingHost, and the SSL certificate is valid but lacks advanced security configurations like HSTS and security headers. Performance is relatively slow due to a large page size and many resources, but mobile optimization and SEO are adequately addressed. From a security perspective, the site implements basic protections including SSL and invisible reCAPTCHA on forms, along with a cookie consent mechanism aligned with GDPR requirements. However, it lacks explicit privacy policies, terms of service, security policies, and incident response information. No vulnerability disclosure or security.txt files were found. The overall security posture is moderate but could be improved with enhanced HTTP headers, DNSSEC, and published security documentation. Overall, Orchestra Brasil presents a professional and consistent online presence supporting Brazilian furniture industry exporters. Strategic improvements in security and compliance documentation would enhance trust and reduce risk exposure.

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

9 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
  2. 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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';…
  3. 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

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

Keep watching orchestrabrasil.com.br

This scan found 22 issues across 6 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
77
Security headers
15
Email security
50
DNS health
85
Network security
60
GDPR outside view
25
Average
52
After the cap
49

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 · found on this site
  • 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

Orchestra Brasil occupies a niche role as a facilitator and promoter of Brazilian furniture industry suppliers in international markets. Its competitive advantage lies in its long-standing partnerships with industry associations like Sindmóveis and support from Apex-Brasil, enabling access to global trade fairs and export opportunities. The business model centers on export promotion rather than direct sales, targeting importers and manufacturers worldwide. Revenue streams likely derive from partnerships, sponsorships, and possibly government or industry funding. The target customer segments include importers seeking Brazilian suppliers and domestic manufacturers aiming to expand exports. Growth indicators include participation in multiple international fairs and a network of nearly 100 suppliers. The partnership ecosystem includes Sindmóveis, Apex-Brasil, and Moodle-based training platforms. The website content and structure reflect a focus on supplier promotion, market education, and lead generation through contact forms and newsletter subscriptions.

Security posture

The current security maturity level of Orchestra Brasil's website is moderate. The presence of a valid SSL certificate and use of Google invisible reCAPTCHA on contact forms demonstrate basic security hygiene. The GDPR cookie consent mechanism indicates awareness of privacy regulations. However, the absence of critical security headers (e.g., HSTS, CSP), lack of DNSSEC, and no published privacy policy or security policy represent compliance gaps and potential vulnerabilities. There is no visible incident response contact or vulnerability disclosure policy, which limits transparency and readiness for security incidents. Data protection practices are partially implemented but lack comprehensive documentation. The security culture appears to be in early to intermediate stages, with room for improvement in formalizing policies and enhancing technical controls.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS and prevent downgrade attacks.
  2. Publish a comprehensive privacy policy and terms of service pages detailing data handling, user rights, and compliance with GDPR.
  3. Implement security-related HTTP headers such as Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy to mitigate common web vulnerabilities.
  4. Enable DNSSEC for the domain to protect against DNS spoofing and improve domain security.
  5. Establish and publish a security policy including incident response procedures and contact channels (e.g., security@ or abuse@ email addresses) to improve transparency and trust.
Technical notes

Notes

The website is built on a WordPress CMS platform with a variety of common plugins for SEO, forms, GDPR compliance, and marketing automation. The tech stack includes jQuery, Google Analytics, Facebook Pixel, and several UI libraries such as Swiper and bxSlider. Hosting is provided by KingHost with both IPv4 and IPv6 DNS records. The SSL certificate is valid but lacks advanced protocol and cipher suite details, and no HSTS is enabled. Performance is slow with a large page size (~3.2MB) and high resource count (308), indicating potential for optimization. Mobile optimization is good, and SEO is supported by Yoast SEO plugin and structured data (JSON-LD). Technical risks include missing security headers and lack of DNSSEC, which could impact business operations if exploited.
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 orchestrabrasil.com.br. 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 orchestrabrasil.com.br.

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.