We do not monitor your internal network devices, it would be illegal to do so unless it was a service you had voluntarily subscribed to. We cannot look at what each device is doing and we cannot log what each device does. In terms of usage data, it is calculated by Telkom and relayed to ISPs. Telkom maintains the authoritative record of usage of customers and any reference to a hack of any system would be one of theirs and not ours, however we do not believe in this case that anything was hacked in any manner whatsoever. In terms of "cyber attacks" how does an ISP know what traffic you are legitimately downloading and what traffic you are not requesting, and how does an ISP know which if that is as a result of unrequested data transfers? The moment you are allocated a public IP in the modern world, the risk of "cyber attack" begins and there is no mechanism with which to know the data residing on every server in the world, nor to know the motive for every packet of data transfer that takes place. If any ISP were to employ "attack mitigation as a service" for every client not only would it be prohibitively expensive, but it would also slow legit traffic down as such systems are not without their own flaws. You end up with a situation where you are having to police every connection on behalf of customers and make decisions on their behalf about what is legit and not, which not only is a precedent that we don't necessary like, but is a process that is almost impossible to get right without knowing the intent of every packet transfer. The other problem is that without "controlling" your internal network and every connected device, even if you had all of the other data, would mean you cannot convert the information into something logical to make a call about on an automated basis.
So the risk of cyber attack by things like DDoS certainly exist over public networks like the internet. We have employed a new system where we are searching for traffic signatures that "detect" if you are a potential host of malicious software and we recently began suspending these services until customers rectified on their end, but even this doesn't stop most attacks. The solution to not being capped by such an event is an uncapped solution. The solution for rectifying on an automated basis to prevent degradation in quality of experience is not one the industry yet has, not from vendors and not from ISPs, at least not in a fool-proof manner. Machine-learning helps, but is not ready yet for commercial deployment and at this stage still wouldn't protect against end-user connections, only core and border equipment. Until then, what is needed is better enforcement against such attacks and more resources from enforcement agencies to allow them to investigate such attacks and hold perpetrators accountable.