Our Security Policy

    in good faith

    PVY.swiss Security Policy

    Below is the full content for the Security Policy page at https://pvy.swiss/security-policy. It follows industry conventions (aligned with ISO 27001 language, OASIS CSAF 2.0 references, and RFC 9116 security.txt semantics) while being tailored to PVY.swiss AG's profile as a Swiss SaaS Vendor with software architecture and engineering consultancy.

    Security Policy — PVY.swiss AG

    Effective Date: 2025-07-11
    Last Reviewed: 2025-07-11
    Version: 1.0
    Owner: André Grüter, Founder & CTO, PVY.swiss AG

    1. Introduction

    PVY.swiss AG ("PVY", "we", "us") is a Swiss-registered Company, specialized in SaaS and technology consultancy for systems architecture, software engineering, and digital infrastructure. We take the security of our systems, our clients' data, and the broader internet ecosystem seriously.

    This policy describes how we handle security vulnerabilities, what you can expect from us if you report one, and how we protect the systems under our control.


    2. Scope

    This policy applies to:
    • All web properties operated by PVY.swiss AG, including pvy.swiss, *.pvy.swiss, and any production services we host on behalf of clients where PVY is the data processor.
    • APIs, backend services, and infrastructure directly managed by PVY.swiss AG.
    • Open-source projects published under PVY.swiss AG's organizational accounts.
    Out of scope:
    • Third-party SaaS platforms we use but do not control (e.g., GitHub, Gitlab,).
    • Client systems where the client is the sole data controller and operator.
    • Social engineering, phishing, or physical attacks against PVY personnel.
    • Denial-of-service (DoS/DDoS) testing — do not perform these.

    3. Reporting a Vulnerability

    If you believe you have discovered a security vulnerability in any PVY.swiss system, we encourage responsible disclosure.

    3.1 Contact

    We strongly recommend encrypting sensitive reports using our PGP key.

    3.2 What to Include

    To help us triage effectively, please include:
    • Description of the vulnerability and its potential impact.
    • Reproduction steps — detailed, step-by-step instructions.
    • Affected URL(s), endpoint(s), or component(s).
    • Your assessment of severity (e.g., using CVSS 3.1/4.0).
    • Any proof-of-concept code or screenshots (do not include client/user data).
    • Your contact details so we can follow up (optional but appreciated).

    3.3 What NOT to Do

    • Do not access, modify, or delete data belonging to other users.
    • Do not degrade service availability (no DoS/DDoS).
    • Do not exploit vulnerabilities beyond the minimum required to demonstrate the issue.
    • Do not publicly disclose the vulnerability before we have had a reasonable opportunity to remediate (see Section 5).

    4. Our Commitment to You

    MilestoneTarget
    AcknowledgmentWithin 2 business days of receipt
    Initial triage & severity assessmentWithin 5 business days
    Status updateAt least every 10 business days until resolution
    Remediation (Critical/High)Target 30 calendar days
    Remediation (Medium/Low)Target 90 calendar days
    We will:
    • Treat your report confidentially.
    • Not pursue legal action against researchers who act in good faith and comply with this policy.
    • Credit you publicly on our [Security Acknowledgments](https://pvy.swiss/security-acknowledgments) page, unless you prefer to remain anonymous.
    • Notify you when the vulnerability has been remediated.

    5. Coordinated Disclosure

    We follow a coordinated disclosure model:
    1. Reporter submits the vulnerability to security@pvy.swiss.
    2. PVY acknowledges, triages, and remediates.
    3. PVY publishes a CSAF advisory (when applicable) at our CSAF provider endpoint https://pvy.swiss/.well-known/csaf/provider-metadata.json .
    4. Reporter may publish their findings after PVY has released a fix or 90 calendar days after the initial report — whichever comes first.
    If we need more time due to the complexity of a fix, we will communicate this transparently and negotiate a revised timeline.
    6. Security Advisories (CSAF)

    PVY.swiss AG publishes security advisories in conformance with the OASIS CSAF 2. https://docs.oasis-open.org/csaf/csaf/v2.0/csaf-v2.0.html standard.

    ResourceURL
    Provider Metadatahttps://pvy.swiss/.well-known/csaf/provider-metadata.json
    PGP Signing Keyhttps://pvy.swiss/pgp-key.txt
    Advisories will be published when vulnerabilities affecting PVY-operated services or PVY-published software are confirmed and remediated.

    7. Infrastructure & Operational Security

    While we do not disclose exhaustive internal controls, the following principles govern our security posture:

    7.1 Data Protection

    • All data in transit is encrypted using TLS 1.2+ (TLS 1.3 preferred, and made where possible).
    • Data at rest is encrypted using AES-256 or higher.
    • We process personal data in compliance with the Swiss Federal Act on Data Protection (FADP/nDSG) and, where applicable, the EU GDPR.

    7.2 Access Control

    • Principle of least privilege enforced across all systems.
    • Multi-factor authentication (MFA) required for all administrative access.
    • Access reviews conducted quarterly.

    7.3 Infrastructure

    • Production workloads run on hardened, regularly patched infrastructure.
    • Container images are scanned for known vulnerabilities (CVEs) before deployment.
    • Secrets management via dedicated vaults — no secrets in source code.

    7.4 Monitoring & Incident Response

    • Centralized logging and anomaly detection on all production systems.
    • Defined incident response procedure with escalation paths.
    • Post-incident reviews conducted for all Severity 1 and 2 events.

    7.5 Supply Chain

    • Dependency updates monitored and triaged via automated tooling.
    • Third-party vendors assessed for security posture before integration.

    8. Client Engagements

    When PVY.swiss AG builds or operates systems on behalf of clients:
    • Security responsibilities are defined in the engagement contract (shared responsibility model).
    • We recommend and implement security controls appropriate to the risk profile of the project.
    • We conduct threat modeling and security reviews as part of our architecture process.
    • Penetration testing is recommended for all production deployments and can be coordinated through PVY.

    9. Hiring

    We are always interested in people who care about building secure, well-architected systems. See current opportunities at:

    🔗 https://pvy.swiss/careers


    10. Legal

    10.1 Safe Harbor

    PVY.swiss AG considers security research conducted in compliance with this policy to be:
    • Authorized under Swiss law (Art. 143/143bis Swiss Criminal Code).
    • Conducted in good faith.
    • Exempt from legal claims by PVY, including DMCA-equivalent claims, provided the researcher complies with Section 3.3.
    This safe harbor does not extend to systems operated by third parties, even if they are linked from PVY.swiss.

    10.2 Governing Law

    This policy is governed by Swiss law. The exclusive place of jurisdiction is the registered domicile of PVY.swiss AG.

    11. Contact

    For general security inquiries: security@pvy.swiss
    For business inquiries: Please use our Contact Form or call in.

    12. Revision History

    VersionDateChanges
    1.02026-06-03Initial publication