On 10/31/26 12:29, Gus Heck wrote:
Every situation is different, and that design is what Solr used to
recommend before we added the rule based auth plugin. It all depends on
how critical internal security is vs external security. Very large
companies sometimes have more risk from internal threats, small companies
can often afford to trust internal folks more. The intent of the auth
plugins we have is to allow for internal security, though I think they
deviate from expected norms and are more complex than they need to be.
Sadly, with the AI bubble of 2026 merging with the cybersecurity bubble
of 2023, it is becoming less and less about the actual security and more
about the theater. And it's only going to get worse.
In our case about the worst thing 3viL h4x0rZ can do by breaking into
Solr, specifically, is to feed visitors false information that is part
of historical record and can be independently verified from any number
of other sources... i.e. not different from said visitors asking
ChatGPT. So the main threats in our environment is internal tenable
scans. And crawler bots that every once in a while find a way to get
past the filters and DDoS the cluster.
(The latest batch, BTW, was searching for `xxx` in a DateRange field and
had enough requests/minute that `SolrExceptoin: Couldn't parse date
becasue: Improperly formatted datetime:xxx` exceptions first pegged the
CPU at 110% which -- presumably -- starved the garbage collector, and
then the entire JVM OOM'ed after a while. That's the actual real-world
threat, not the CVE rubbish that take the entire Calude months to find
and tens of hours to actually exploit.)
Dima
