Te volume and sophistication of attacks continue to grow, and the rise of AI is accelerating that. We’re seeing malicious actors train AI to replicate and scale their own
attack methods. Tat’s what keeps me up at night - not the lone hacker, but the automation of malicious behaviour.
Community Immunity Continent 8 launches Threat Exchange
Chief Security Officer Patrick Gardner explains how the new Threat Exchange platform empowers operators, suppliers, and regulators to collaborate against a rising tide of cyber threats targeting gaming.
Patrick, let’s start with the basics: what exactly is Treat Exchange?
Te Treat Exchange is the most comprehensive source of threat intelligence built specifically for the gaming industry. For over 25 years, Continent 8 has provided hosting, connectivity, and security solutions, and during that time we’ve accumulated a vast database of indicators of compromise; essentially data points linked to bad actors targeting gaming companies. Treat Exchange takes all that intelligence and distils it into actionable insights that help the industry proactively detect, analyse, and prevent attacks.
How does the Treat Exchange work in practice?
It’s both a data repository and a live intelligence platform. We currently have more than six million indicators of compromise, things like malicious IP addresses, email domains, and file hashes. Users can interact with the database through a threat intelligence interface to investigate potential incidents. But it’s not just static data; operators can subscribe to live data feeds that automatically integrate with their own systems; firewalls, web application firewalls, and other security controls, to block known threats before they can act.
Te name “Exchange” suggests collaboration. How important is that element?
It’s central. Continent 8 already has huge visibility into gaming traffic globally, we handle roughly 90 per cent of all iGaming data flows
68
worldwide, but we only see what happens in our data centres. Our customers, on the other hand, have their own corporate networks and security operations with intelligence we don’t see directly. Te Exchange allows both sides to share information. If one customer detects a bad actor, that intelligence can be fed back into the Exchange and redistributed to others. It’s about building community immunity through collaboration.
What kind of data are companies sharing and how do they contribute?
Contributions can be manual or automated. Manually, a security analyst can log in, create an indicator, and upload details of a phishing domain or malicious IP. But automation is the goal. For example, our Managed SOC services can integrate with a customer’s infrastructure and automatically feed anonymised threat data into the Exchange. Tis way, the industry learns collectively and in real time.
How reliable is the information being shared, given the scale of data?
Accuracy is everything. Tere’s a lot of “noise” in open-source threat intelligence; millions of data points, many of them false positives. We apply scoring and validation models to ensure what we share has a high confidence level. For example, when a customer confirms a detected threat is genuine, that reinforces its credibility within the platform. Each data point is given a confidence score, and older
PATRICK GARDNER Chief Security Officer Continent 8 Technologies
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164 |
Page 165 |
Page 166 |
Page 167 |
Page 168 |
Page 169 |
Page 170 |
Page 171 |
Page 172 |
Page 173 |
Page 174 |
Page 175 |
Page 176 |
Page 177 |
Page 178 |
Page 179 |
Page 180 |
Page 181 |
Page 182 |
Page 183 |
Page 184 |
Page 185 |
Page 186 |
Page 187 |
Page 188 |
Page 189 |
Page 190 |
Page 191 |
Page 192 |
Page 193 |
Page 194
