Trust center

Security belongs in the work, not just the pitch.

We focus on practical controls, responsible disclosure and clear boundaries. We do not claim certifications we have not independently earned.

Security specialist reviewing access controls on a screen

CLEAR BOUNDARIES

No unsupported certification claims.

Specific controls are confirmed per engagement.

CONTROLS · DISCLOSURE · BOUNDARIES

Controls we design for

Least-privilege access
MFA where supported
Secrets kept out of public code
HTTPS / TLS in production

Clear boundaries

What we do — and what we don’t claim.

Trust comes from being specific. This is how VSN approaches security in delivery, and where its responsibilities and claims stop.

WHAT WE DO

Practical controls, built into delivery.

Design delivery around practical engineering controls: least-privilege access, MFA, secrets management, dependency hygiene, secure transport and change review.

Handle security reports privately through VSN’s published security contact.

Agree shared responsibilities for scope, access, delivery and handover with each client.

Confirm specific controls in the proposal or security questionnaire for each engagement.

WHAT WE DON’T CLAIM

No borrowed badges or blanket promises.

SOC 2, ISO 27001, PCI DSS or any other certification — unless a valid certification is published separately.

That one control set fits every project, hosting platform and client requirement.

Control over customer-owned user permissions, source data, third-party accounts or legal and compliance obligations.

Certifications or audits VSN has not independently earned.

Engineering practices

Controls we design for.

Specific controls can vary by project, hosting platform and client requirements. They should be confirmed in the proposal or security questionnaire for each engagement.

CONTROL 01

Least-privilege access

Prefer role-based accounts and only the access needed for delivery. Avoid unnecessary sharing of master credentials.

CONTROL 02

MFA where supported

Use multi-factor authentication on critical delivery, hosting and administrative systems where the platform supports it.

CONTROL 03

Secrets management

Keep production secrets out of public repositories and client-side code; use environment or platform secret stores.

CONTROL 04

Dependency hygiene

Review dependencies, patch known issues and avoid adding packages without a clear need.

CONTROL 05

Secure transport

Production websites and APIs should use HTTPS/TLS, with secure headers appropriate to the application.

CONTROL 06

Change review & QA

Use review points, testing and deployment checks proportionate to project risk before production changes.

Responsible disclosure

Found a security issue?

Use VSN’s published security contact so reports can be handled privately. Do not include sensitive customer data unless it is necessary to explain the issue.

Report a security issue

PUBLIC SECURITY CONTACT

Coordinated reporting

Security researchers should act in good faith, avoid privacy violations, service disruption or destructive testing, and allow reasonable time for investigation and remediation.

/.well-known/security.txt
Contact: mailto:info@vertexsystemsnetwork.com
mailto:info@vertexsystemsnetwork.com
Expires: 2027-10-01T00:00:00Z
Preferred-Languages: en
Act in good faith Avoid privacy violations No disruption or destructive testing Allow reasonable time to remediate

Client data

Security responsibilities are shared.

VSN can build and operate technical controls, but customers also control user permissions, source data, third-party accounts and their own legal/compliance obligations.

01 / STEP

Scope

Define data types, environments, access needs and third-party processors before high-risk work begins.

02 / STEP

Access

Use named accounts, MFA and revocation procedures instead of permanent shared credentials where possible.

03 / STEP

Delivery

Separate test and production work, protect secrets and document high-impact configuration changes.

04 / STEP

Handover

Rotate temporary access, transfer ownership and document ongoing operational responsibilities.

VSN CAN

Build and operate technical controls agreed in the engagement scope.

CUSTOMERS CONTROL

User permissions, source data, third-party accounts and their own legal/compliance obligations.

Security requirements

Have security requirements?

Include hosting, data sensitivity, access, compliance and procurement requirements in the project brief so they can be scoped before development.