Skip to content

This site is shown in English. Switch language if you prefer.

Menu

Monday to Saturday, 9:30 am to 6:30 pm India time (IST)

Contact us

Software quality and security practices

How AcmaSoft keeps the software it builds reliable and the data it handles safe: code review, testing, continuous integration, access control, backups and privacy by default. These are the practices we use on projects, adjusted to each client and the rules they must follow.

  • 17+years of experience
  • 2,000+projects delivered
  • 300+products shipped

Quality and security are planned from day one

Quality and security are hard to add at the end of a project. We plan them from discovery: requirements include performance, security and accessibility needs, and each phase has checks before work moves on.

This page describes how we work on projects, not a certification. If your organisation needs a specific certification, audit or compliance framework, tell us during discovery and we will say plainly what we can support.

On every project

  • Peer review before code is merged
  • Testing in every sprint
  • Separate staging and production
  • Least-privilege access to systems
  • Credentials kept out of the code
  • Backups for the systems we maintain

How we assure software quality

Six practices that catch most defects before your users do.

  • Code review

    Every change is reviewed by another developer before it is merged, for logic, readability, security and the coding standards of the stack.

  • Standards and static analysis

    We follow the usual conventions for each stack, such as PSR for PHP or a framework's own style guide, and run linters and static analysis to catch problems early.

  • Testing every sprint

    Functional, regression, browser and device testing in each sprint, with automated unit and integration tests where the budget and lifespan of the project justify them.

  • Continuous integration

    Builds and checks run automatically when code is pushed, with services such as GitHub Actions, GitLab CI or Bitbucket Pipelines, so broken changes stop before staging.

  • Performance and accessibility

    Before launch we check page speed and Core Web Vitals, plus the accessibility basics: contrast, keyboard use, headings and image alt text.

  • Acceptance and release

    You test each release on staging against the agreed acceptance criteria. Releases follow a checklist with a rollback plan.

Secure development basics

Security follows the software from the first line of code to the live server.

  • Secure coding

    We validate input, escape output, use prepared database queries and work through the OWASP Top 10 as a checklist of common web risks.

  • Dependencies and updates

    Frameworks, plugins and libraries are kept up to date, and dependencies are checked for known vulnerabilities before a release.

  • Secrets and credentials

    Passwords, API keys and tokens live in environment configuration or a secrets store, never in the code repository.

  • Encrypted connections

    Sites and APIs run over HTTPS so data is encrypted in transit, and stored data is encrypted as well where a project calls for it.

Access control, backups and data privacy

Your systems and data are handled on a need-to-know basis, and access ends when the work does.

Least-privilege access

Team members get only the access their role needs, with individual accounts instead of shared logins wherever the system allows it.

Two-factor authentication

We turn on two-factor authentication for code repositories, hosting panels and admin accounts where the service supports it.

Access reviews and offboarding

Access is reviewed when people join or leave a project and removed at the end of an engagement.

Backups and recovery

For the sites and applications we host or maintain, we schedule regular backups stored apart from the live server and check that they restore.

Data privacy

We work with test or anonymised data where we can, collect only the personal data a feature needs, and design forms and consent with laws such as GDPR in mind.

Confidentiality

Project information stays with the people working on it, and we sign a non-disclosure agreement on request.

Quality and security checks in each phase

The checks follow the six phases of our development methodology.

Read our development methodology

Discovery

Quality

  • Acceptance criteria
  • Non-functional requirements

Security

  • Data and risk review
  • Compliance needs

Design

Quality

  • Prototype testing
  • Accessibility review

Security

  • User roles and permissions
  • Data flow review

Build

Quality

  • Code review
  • Automated checks

Security

  • Secure coding
  • Dependency checks

Release

Quality

  • Regression testing
  • User acceptance testing

Security

  • Secrets review
  • HTTPS and server settings

Support

Quality

  • Monitoring and fixes
  • Planned updates

Security

  • Security patches
  • Backups and access reviews

Handling sensitive data? Tell us the rules you work under.

Ask a security question

Questions about quality and security

Your security team may have a questionnaire. Send it and we will answer it.

Ask a question
Do you hold a security certification?

This page describes our working practices, not a certification. If your project requires a certified supplier, ask during discovery and we will confirm what we can provide.

Can you sign an NDA before we share details?

Yes. We can sign a non-disclosure agreement before you share requirements, documents or access.

Do you run security testing?

Security checks are part of our testing, such as reviewing common OWASP risks and known dependency vulnerabilities. For high-risk systems we recommend an independent penetration test and fix what it finds.

Who has access to our production systems?

Only the team members who need it for their role, with individual accounts. We keep a list of who has access and remove it when the engagement ends.

How do you handle personal data in testing?

We prefer test or anonymised data. When real data is needed, it stays in secured environments and is deleted when it is no longer needed.

Discuss your quality and security needs

Tell us about the project, the data it handles and any rules you must follow. We will reply with how we would build and run it safely.

Estimated budget (optional)

Goals, users, key features and any deadline.0 / 2,000

Attachment (optional)

Protected against spam without puzzles. We never share your details.

Choose your region & language

Americas

Asia-Pacific

Europe, Middle East and Africa

Translations are produced automatically by Google Translate.