What we are certified to

ISO 9001:2015

Quality Management System

Establishes how we plan, deliver and improve our products and services so that customer requirements are met consistently.

CertificateAMER21536
ISO/IEC 27001:2022

Information Security Management System

Establishes how we identify, treat and monitor information security risks across people, processes and technology.

CertificateAMER21537
Scope
Design, development, validation and support of the suite of software products and services
Issued
12 October 2024
Recertification due
11 October 2027
Certification body
Americo Quality Standards Registech, accredited by UAF. Verify at americocert.com

Two systems, two different jobs

A quality management system helps an organisation do the right things, the right way, every time. An information security management system protects the information that work depends on. They answer different questions, and we run both.

QMS · ISO 9001:2015ISMS · ISO/IEC 27001:2022
FocusQuality of products and servicesProtection of information assets
Primary objectiveCustomer satisfactionInformation security
Key concernMeeting requirements consistentlyManaging security risks (CIA)
StandardISO 9001:2015ISO/IEC 27001:2022
Success measureQuality, efficiency, customer satisfactionConfidentiality, integrity, availability

Together they let us operate effectively and securely, and keep improving both.

What information security actually protects

Information can be stolen, altered without authorisation, lost, disclosed to the wrong people, or made unavailable exactly when it is needed. Every control we run exists to protect one of three properties.

Confidentiality

Information is exposed only to authorised parties. Access and disclosure are controlled.

Integrity

Information stays accurate and complete. Unauthorised alteration is prevented and detected.

Availability

Information and systems are reachable when they are needed. Reliability and uptime are part of security.

Controls that stop, spot and recover

Security controls are not one thing. Each type acts at a different moment relative to an incident, and a working ISMS needs all three.

Preventive

Before an event

Stop incidents from occurring

  • Multi-factor authentication
  • Data encryption
  • Access control policies

Detective

During or after an event

Identify incidents as they happen

  • Audit logs and monitoring
  • Security alerts
  • Internal audits

Corrective

After an event

Recover and reduce impact

  • Backup and restore
  • Incident response plans
  • Vulnerability patching

Document control, because an outdated procedure is a real risk

If a team follows a superseded procedure, the wrong process gets used: defects are introduced, security controls are missed, and audits find gaps. Document control is the systematic management of a document from creation through to disposal, so the right people always use the right version.

  1. 01CreationPrepared in the standard template so nothing required is left out.
  2. 02ReviewChecked for technical accuracy, completeness and clarity.
  3. 03ApprovalFormally authorised for official use.
  4. 04Version controlChanges tracked over time so everyone knows what is current.
  5. 05DistributionAccess given to the current version, not an old copy.
  6. 06RetentionRecords preserved for future reference and audit.
  7. 07Archival & disposalObsolete documents removed safely so they cannot be followed by mistake.

Every controlled document has four roles

Author

Drafts and updates the document, and is accountable for the content being accurate, current and complete.

Reviewer

Verifies technical accuracy, completeness, clarity and alignment with organisational requirements before approval.

Approver

Formally authorises the document, confirming it meets the required standards and is ready for distribution.

Users

Follow the approved version of the document in their day-to-day work.

Policy, procedure, SOP: three different documents

These are often used interchangeably. They are not the same thing, and knowing which one you are reading tells you how much detail to expect and who owns it.

Policy

What should be done, and why

Detail
High level
Audience
Entire organisation
Owner
Top management
Format
Short statements and principles

Information Security Policy · Quality Policy

Procedure

Who does it, when, and in what major steps

Detail
Medium level
Audience
Process owners and teams
Owner
Process owner
Format
Workflow with roles and responsibilities

Incident Management Procedure · Corrective Action Procedure

SOP

Exactly how the task is performed

Detail
Highly detailed
Audience
Operational users performing the task
Owner
Functional team or subject-matter expert
Format
Instructions, screenshots, checklists

SOP for reporting a security incident · SOP for raising a CAPA

The policies in full

A policy states management’s intent, direction and expectations. These two are the top of our documentation hierarchy: every procedure and SOP below them has to be consistent with what they say.

Quality policy

Vegam Smart Factory Solutions Pvt Ltd is committed to improving customer satisfaction and the strategic direction of the organisation in delivering services through:

  • Design and development of products and services that meet or exceed industry and client requirements
  • Setting quality objectives and monitoring the performance of each function
  • Development of human resources with the required competency and integrity
  • Implementation of technology that enables quality improvement
  • Continual improvement in the effectiveness of the quality management system
OwnerTop managementReviewedAnnually

Information security policy

The purpose of the ISMS is to protect information assets from internal and external threats, and to continually improve and maintain its integrity. Vegam commits to a secure environment through:

  • Safe and secure transmission, handling and processing of customer, resource and organisation data
  • Access for authorised personnel only, for the time required to maintain integrity
  • Comprehensive consideration of business, regulatory and contractual security obligations
  • Formal validation of controls for confidentiality, integrity and availability
  • Information security awareness training for all staff
  • Business continuity planning and proper backup
OwnerTop managementReviewedAnnually

Both ISO standards require ongoing monitoring, measurement, audit and improvement. Certification is not a one-time exercise, and neither is the work behind it.

Need something for your vendor assessment?

If your procurement or quality team needs the certificates, the scope statement, or answers to a security questionnaire, ask and we will send them.