Skip to main content

Security report for e-lvm.lv

Latvijas Valsts Meži · Energy · Latvia

Medium risk. 8 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

57/100

Risk levelMedium

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

Latvijas Valsts Meži operates a secure partner portal at www.e-lvm.lv, providing authenticated access to its cooperation partners. The portal supports multiple strong authentication methods including Smart-ID and bank IDs, reflecting a mature approach to user security. The website is professionally designed with good mobile optimization and clear navigation, targeting business partners in the forestry and energy sector in Latvia. Technical infrastructure is based on modern JavaScript frameworks such as Vue.js and PrimeVue, indicating a contemporary technology stack. Security posture is solid with HTTPS enforced and no visible vulnerabilities, though explicit security headers and incident response information are absent. Privacy compliance is supported by accessible privacy and cookie policies with consent mechanisms. Overall, the website demonstrates a high level of business credibility and trustworthiness consistent with a large state-owned enterprise.

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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  3. 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 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';…

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

Keep watching e-lvm.lv

This scan found 27 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
67
Security headers
60
Email security
40
DNS health
50
Network security
100
GDPR outside view
25
Average
57

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

The portal serves as a B2B collaboration platform for Latvijas Valsts Meži, a key player in Latvia's forestry and energy sectors. Its business model focuses on secure partner engagement and service delivery. The company enjoys a strong market position as a state enterprise with a large operational scale. The portal's ecosystem includes integration with national authentication services and custom analytics, supporting operational insights. The absence of advertising and affiliate programs aligns with its public-sector nature. The business maintains clear contact channels and legal information, reinforcing transparency and trust.

Security posture

Security maturity is moderate to high, with enforced HTTPS and multiple secure login options. However, the lack of visible security headers such as Content Security Policy or HSTS reduces the overall security score. No vulnerability disclosure or incident response contacts are published, which could hinder rapid response to security incidents. Data protection practices appear compliant with GDPR, supported by privacy policies and cookie consent. No exposed sensitive data or vulnerable libraries were detected in the provided content. Recommendations include enhancing HTTP security headers and publishing security policies to improve resilience and transparency.

Recommendations

  1. Implement comprehensive HTTP security headers including CSP, HSTS, and X-Frame-Options.
  2. Publish a dedicated security policy and incident response contact information.
  3. Introduce a vulnerability disclosure program or security.txt file to facilitate responsible reporting.
  4. Enhance accessibility features to improve compliance and user experience.
  5. Regularly audit third-party scripts and analytics for privacy compliance and security.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Latvijas Valsts Meži
Description
Portal for cooperation partners of Latvijas Valsts Meži, providing authentication and access to partner services.
Key services
Partner authentication, Access to partner portal services
Content quality
good
Branding
consistent

Technology

Stack
Vue.js, PrimeVue, JavaScript ES Modules
Frameworks
Vue.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by URL)
  • Multiple strong authentication methods (Smart-ID, bank IDs, eID)

Analytics and tracking

Services
Custom analytics at analytics.lvm.lv
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is a partner login portal for Latvijas Valsts Meži.
  2. Multiple secure authentication methods are offered.
  3. Privacy and cookie policies are present and accessible.
  4. Contact information is clearly provided in the footer.
  5. No signs of malicious or suspicious content.
  6. No explicit security headers detected in provided data.
  7. No visible vulnerability disclosure or security contact info.
Technical notes

Notes

The website uses a modern front-end stack with Vue.js and PrimeVue components, leveraging ES modules for efficient loading. The design is responsive and mobile-friendly, with a clean and professional UI. Performance is moderate, with no evident blocking scripts or heavy resources. SEO optimization is basic, with minimal meta tags and no structured data like JSON-LD detected. Hosting details are not disclosed, and no CMS is identified, suggesting a custom-built platform. Accessibility is basic, with some ARIA roles and focus management present but could be improved. Overall, the technical implementation supports the business needs but has room for enhancements in SEO and accessibility.
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

Earlier scans of this domain

  1. 58/100Medium34 findingsView report
Reviews of this site

Share your experience with e-lvm.lv. 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 e-lvm.lv.

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.