Security and privacy
How ProboIT protects the software we build and run for clients, and the information in it.
We are implementing an information security management system aligned with ISO/IEC 27001:2022, with privacy controls aligned with ISO/IEC 27701 and POPIA, and preparing for certification by an accredited certification body. We are not certified yet, and we will say so here when we are.
Information security
Our management system covers the client platforms we build, host and support. The controls below are in place on the platforms in its scope.
Our information security policy, risk assessment and procedures are written down, kept under version control, and reviewed at least once a year.
Access
- Everyone signs in with their own account. There are no shared logins.
- What someone can see and do depends on their role.
- Administrators must use two-factor sign-in with an authenticator app.
- Passwords are stored only as strong one-way hashes. Repeated failed sign-ins are slowed down.
- Our servers accept key-based sign-in only, never passwords.
Encryption
- All traffic uses HTTPS, and browsers are told to use HTTPS only.
- Database backups are encrypted (AES-256).
- Passwords and keys for clients' connected systems are encrypted (AES-256-GCM) and never shown again after they are saved.
Hosting and backups
- Platforms run on servers in South Africa, kept up to date with automatic security updates.
- Databases are backed up every night and encrypted, and a full restore is tested every month. A backup is also taken before every change is deployed.
Building software
- Every change is checked by automated tests before it goes live, and deployed only with approval.
- Software libraries are checked for known vulnerabilities on every change; serious ones block a release.
- Pages carry security headers that limit where scripts may come from and stop other sites framing them.
Records, incidents and suppliers
- Important actions are recorded in an audit log: who did what, when and from where.
- We follow a written incident response procedure. If personal information is affected, we tell our client straight away. The Information Regulator and the people affected are told as POPIA requires.
- We use a small number of suppliers, chosen and reviewed for their security.
Privacy
This section covers proboit.co.za and how ProboIT handles the personal information of the people we deal with. Under the Protection of Personal Information Act 4 of 2013 (POPIA), ProboIT is the responsible party for this information.
For the platforms we run for clients, the client is the responsible party and ProboIT is its operator. Each platform has its own privacy notice, shown inside that platform.
What we collect on this site
- This site sets no cookies and has no analytics or advertising trackers.
- Its font comes from Google Fonts, so your browser connects to Google's servers to load it.
- If you email us or message us on WhatsApp, we receive your name, contact details and message. We use them only to reply and to work with you. WhatsApp is run by Meta.
How long we keep it, and who sees it
We keep your messages for as long as we are talking or working together, and as the law requires after that. We do not sell or share your information for marketing. Our email and messaging providers process it on our behalf.
Your rights
You can ask what information we hold about you, and ask us to correct or delete it, or to stop using it. Write to our Information Officer. We answer within 30 days. If you are not satisfied, you may complain to the Information Regulator.
Thabelo, ProboIT · thabelo@proboit.co.za
Report a security problem
If you believe you have found a security weakness in proboit.co.za or in a platform we run, please tell us. We appreciate reports made in good faith.
Email thabelo@proboit.co.za with "Security" in the subject. Include what you found and where, how to reproduce it, what an attacker could do, and how to reach you. Please keep it private until we have fixed it.
- We confirm we have your report within 3 working days, and keep you informed until it is fixed.
- Use only your own account or test accounts we give you. Do not look at, change or delete other people's information. Stop as soon as you have shown the problem.
- No load or denial-of-service testing, no phishing or social engineering, and no testing of physical security or our suppliers' systems.
If you follow these rules and act in good faith, we will not take legal action against you for your research. We do not run a paid bug bounty.
Machine-readable contact details: /.well-known/security.txt