Website Security:
SerenaVillage.NET is a secure website and has been online since 2017.
You can verify the reliability of SerenaVillage.NET through the Google Safe Browsing system.
Google is a Global Leader in the Internet industry.
Click here to check security on Google.
SerenaVillage.NET is committed to observing the necessary precautions to guarantee the security of all customers.
Maximum security level for all SerenaVillage.NET customers
Book securely on the SerenaVillage.NET website.
Pioneers in Cybersecurity:
SerenaVillage.NET uses only secure connections with an SSL Certificate Security Grade A+.
Click to check SSL Certificate security.
Maximum A+ Certification:
SerenaVillage.NET adopts a high-tech system and secure connections with the new TLS 1.3, HSTS, DNSSEC, HTTP 3.0, and SSL Full (Strict) systems. For issues related to SerenaVillage.NET site security, you can read our Privacy Policy page.
We also adopt all the latest extreme security techniques to protect customer data in forms, using the newest and most secure CSP nonce system, applying the following extreme security CSP in all server security headers: default-src 'none'; style-src 'self' 'nonce-'; style-src-attr 'none'; script-src 'self' 'nonce-'; and also require-trusted-types-for 'script'. As shown in the image below, you can view the Security Certification Grade A+ for our SerenaVillage.NET server headers.

Absolute Blocking by Default:
This is the fundamental directive of extreme security using CSP default-src 'none'.
It states that no resources (images, scripts, styles, fonts, etc.) can be loaded unless explicitly allowed by a more specific directive.
Security Purpose: It forces the developer to strictly whitelist absolutely everything. If an attacker manages to inject a tag like img src= or script src=, these requests will automatically fail because they are not allowed.
Secure Loading of Styles and Scripts:
These directives allow the loading of: Resources coming from the same origin as the page ('self').
Inline styles and scripts (inside style or script tags) or files that contain a nonce attribute that matches a randomly generated, single-use value that the server includes in the HTTP header and in the HTML tags.
Extreme Security Purpose (Noncing): The use of the newest and most secure CSP nonce system prevents almost all XSS.
An attacker injecting malicious code does not know the secret nonce value for the current request, so their injected script will simply be blocked by the browser.
This is much safer than using hashes or simply allowing inline scripts ('unsafe-inline').
Blocking of Styles in Attributes:
Description (style-src-attr 'none'): This directive prohibits the use of CSS in HTML attributes, such as style="...CSS styles.
Security Purpose: It prevents a common and subtle form of XSS code injection or CSP bypass where an attacker could manipulate the page's appearance or attempt to execute code through vulnerable CSS properties.
Required Trusted Types:
Description (require-trusted-types-for 'script'): This is a cutting-edge security feature (Trusted Types). It demands that DOM functions that handle text strings as code (e.g., innerHTML, document.write) only accept a special object called a "Trusted Type" and not a simple text string.
Extreme Security Purpose: Completely blocks the last line of defense against XSS attacks. Even if the attacker manages to inject a text string into one of these DOM functions, the browser will reject it because it is not a trusted type object.
It is the highest security standard for preventing client-side code injection.
🔑 What It Serves - Final CSP Goal:
The main goal of this extreme security CSP is to protect customer data in forms by:
- Preventing malicious code execution (XSS): An attacker cannot inject scripts into the page to steal session cookies, authentication tokens, or form credentials.
- Ensuring content integrity: It ensures that only authorized and server-verified resources (scripts, styles) are executed, preventing the page from loading code from external or untrusted sources.
- Reinforcing XSS mitigation (Defense in Depth): By using nonce and require-trusted-types-for 'script', multiple layers of protection are created, ensuring that even minor input validation failures do not result in a critical vulnerability.
In summary, this CSP configuration is an advanced shield that ensures the web application only loads the resources the developer intended, neutralizing code injection attempts and elevating security to a level far superior to the average.

Maximum Cookie Policy Security:
Our default Cookie Policy on the SerenaVillage.NET server is: path=/;max-age=1440;SameSite=Strict;Secure.
This serves to limit the cookie duration and use only secure, first-party cookies that are deleted after booking, and is a highly recommended practice to reinforce user privacy and security.
In summary, the cookie policy implemented by SerenaVillage.NET demonstrates a strong commitment to user privacy and security through the following recommended practices:
- Appropriate cookie scope (path=/).
- Protection against CSRF (SameSite=Strict).
- Protection against "Man-in-the-Middle" attack (Cookie Secure).
- Limited cookie lifetime of 24 minutes (max-age=1440).
- Minimization of third-party cookie usage.
- Proactive deletion of cookies after booking and necessary use.
Cookie Policy Objective:
path=/: This ensures that the cookie is valid for all paths within the SerenaVillage.NET domain.
SameSite=Strict: This attribute is the MAXIMUM SECURITY OPTION available and guarantees the best protection against Cross-Site Request Forgery (CSRF) attacks. A cookie with Strict is NEVER sent if the user accesses our site from a link or request originated from an external site. It is only sent in requests that originate from the same website.
Secure: The Secure attribute is a critical security measure. When present, it instructs the browser that the cookie should only be sent over secure connections encrypted with (HTTPS).
What does it do?: It prevents the cookie from being accidentally sent over an unencrypted HTTP connection (in plain text).
Why is it important?: If an attacker is intercepting traffic on a public Wi-Fi network, for example, and the site attempts to load a resource via HTTP, with Secure the browser will not deliver the cookie, protecting it from being stolen through a "Man-in-the-Middle" attack.
🛡️ UNBREAKABLE SECURITY 🛡️: By implementing Strict, we eliminate any window of opportunity for a session to be potentially hijacked or used by a third party, even if the attacker tricks the user into clicking a malicious link.
max-age=1440: Setting the maximum cookie lifetime to 1440 seconds (24 minutes) is an excellent security and privacy practice. This limits the time during which a cookie can be used, reducing the window of opportunity for its exploitation in case of a security breach or unauthorized access.
Exclusive use of first-party cookies: By using only cookies generated and managed directly by the SerenaVillage.NET domain, the risk associated with third-party cookies is significantly reduced, as they are often used for cross-site tracking and can raise privacy concerns.
Cookie cancellation after booking: This is a proactive privacy measure. Once the booking is complete and the information is no longer needed in a cookie, deleting it minimizes unnecessary retention of personal data, which is essential for user privacy.
These measures complement the HTTP security header policies and contribute to creating a safer and more privacy-respecting online environment for users of SerenaVillage.NET. It is an excellent strategy for building trust among website visitors.

