You said · We had a breach or close call
Industry · RTO or education
A breach just happened and we need to stop it from happening again.
The invoice redirection hit the accounts team. Or the phishing link bypassed your email gateway. Or the ransomware tried to encrypt the VETtrak database. The first hour is about containment. The first week is about evidence preservation. The first month is about proving to your regulator that you have fixed the hole.
What this usually looks like
What a security incident looks like for an RTO.
You are holding sensitive data under the Privacy Act and state funding requirements. A Business Email Compromise might have diverted training fees. A leaked credential set could expose USI records. The immediate fear is financial loss. The longer-term fear is ASQA scrutiny under the 2025 Standards effective 1 July 2025.
Your stack includes aXcelerate, Wisenet, and VETtrak. These are not hardened by default. If an attacker gains access to an admin account, they can alter student results, manipulate attendance, or export personal data. The cyber insurance questionnaire from your state funding body will ask about your incident response plan. If you do not have one, your premium jumps or coverage drops.
The pain is not just technical. It is administrative. You need to notify affected students. You need to report to ASQA if there is a breach of the Registered Training Organisations Standards. You need to restore AVETMISS submissions without losing data integrity. Panic leads to bad choices. A structured response leads to recovery.
Where we'd start
What we would do in the first fourteen days.
-
Step 01
Contain and preserve evidence
We isolate the compromised endpoints and revoke active sessions immediately. We preserve logs from your email gateway, firewall, and VET management systems. We work with your cyber insurance provider to ensure the response is covered. We stop the bleed before we start the repair. This protects your legal position and your data.
-
Step 02
Secure the VET data environment
We audit access to aXcelerate, Wisenet, and VETtrak. We enforce MFA on all administrative accounts. We check for persistence mechanisms like rogue API keys or scheduled tasks. We verify backup integrity for USI and student records. We ensure the systems are clean before we restore operations. We do not trust the previous state.
-
Step 03
Document the response for ASQA
We produce a clear timeline of events and actions taken. We map the incident to the Essential Eight maturity levels. We create a remediation plan that aligns with the 2025 Standards. We help you draft the notification if required. We turn a security failure into a compliance demonstration. This is how you regain trust.
How we handle security
We hold the security decisions in every environment we run.
Every client we take on runs to a set of controls we set: phish-resistant MFA, allowlisted applications, known vulnerabilities closed inside thirty days, backups that have actually been restored, and access cut the day someone leaves. Where one of those genuinely does not fit how a business works, we agree an alternative in writing rather than let it lapse.
Security and convenience pull against each other, and we would rather have the argument about where the line sits than pretend there isn't one. Some of those arguments end with us changing our mind. What we won't do is wave through a change we think ends in a breach, because we carry that incident with you. If you want a provider who actions every request without asking what it costs you, we're the wrong firm.
-
We set the standard, not the client
Every environment we run meets the same security controls, on every plan. It is not a menu and it is not priced separately.
-
Exceptions are agreed and written down
Where a control genuinely does not fit how a business works, we negotiate an alternative and record what we accepted instead. Nobody has to guess later.
-
We can say no to a change
If a request would leave you exposed, we will say so and we will not action it quietly. Convenience is worth arguing about. A breach is not.
What each plan runs
The full set of controls, and which plan carries which, sits in the plan detail.
Track record
Twenty years in. A hundred-plus clients. The numbers are load-bearing.
- Years in business
- 20+
- Loved clients
- 100+
- Aussie techs
- 100%
4.8 average · 46 reviews on Google
“We're on a monthly plan across all four of our sites, two of them interstate. PCs stay healthy, licences current, and the team understand our needs well.”
“Night and day working with CCP. They came in from day one, spent the time to ensure everything was set up and secure properly, and now everything just works. Due to the success we've had with them, we further engaged them to manage our phone systems and website. If you work with CCP you will never have to worry about your IT systems again.”
“We have been using CCP since the early 2000s and have always had great service on our 20-plus PCs and server. We recently moved to a managed service and cannot rate the experience highly enough. Well done Lee and team.”
“Walked through the other quotes we had and explained in detail what services we needed and what we didn't. They came in 50% cheaper. Just good, honest, straight-shooting people.”
“We have been continually impressed with CCP over the several years we have used them. They are extremely efficient, excellent customer service and well priced. I would recommend Lee and his team.”
The qualifier
Let's see if we're a fit.
Seven questions, one moment of your time. We'd rather tell you now than three months in.