VOLOVLOAutomation risk & transition, task by task
AskOccupationsMajorsBusinessFoundersChangesNotesMethod
Search occupations, majors…
EN
  • English
  • 简体中文
  • 日本語
  • Español
  • Português
  • Français
VLO
VOLO

Understanding how automation changes work — task by task, with the evidence shown and the uncertainty admitted.

AskOccupationsMajorsBusinessFoundersChangesNotesMethodWill AI replace my job?AboutRole diagnosisOpen dataOntologyVOLO ProPrivacyTerms
© 2026 VOLO
Guides
Ask VOLOFor businessFor foundersRecent changesNotesRole diagnosisFirst AI experimentVOLO ProMethod & evidenceAboutFollow an occupationSearch
Occupations
All occupations
AI / software
Translator / InterpreterBank tellerCopywriterContent moderatorCustomer service representativeAdministrative assistantSoftware tester / QA engineerGraphic designerParalegalVideo editorAccountant / BookkeeperMarketing specialistFrontend developerTax preparer / tax agentVoice actorMedical coderData analystInsurance claims handlerTechnical writer / documentation engineerJunior software developerInsurance underwriterHR / recruiterLoan officer / credit officerFinancial analystProcurement / supply chain specialistJournalistSales / account managerReal estate agentIT support specialist / helpdeskAuditorManagement consultantBackend developerAI researcherProduct / UX designerBusiness systems ownerE-commerce operations specialistActuaryRadiologistData engineerProject managerLawyerMedical assistant / clinic assistantQuantity surveyorMachine learning engineerExperienced software engineerDevOps / platform / SRE engineerProduct managerPharmacistPartnerships / channel managerSecurity analyst (SOC)Financial adviser / financial plannerCompliance officerLibrarianArchitectFirst-line manager / team supervisorCounsellor / therapistRetail salesperson / shop assistantCivil / structural engineerSecurity guardBus driverInsurance agentSchool teacherGeneral practitioner / primary care doctorAirline pilotWaiter / restaurant serverRadiographer / radiologic technologistAuto mechanic / vehicle technicianPolice officerSonographerAir traffic controllerVeterinarianPhysiotherapist / rehabilitation therapistDentistConstruction workerSocial workerRegistered nurseCare worker / nursing assistantPlumberAI implementation lead
RPA / self-service
Government service clerkOperations coordinatorMetro train driverReceptionist / front desk
Robotics
Retail cashier / shop assistantContainer port workerWarehouse workerAssembly line workerMedical laboratory technicianWelderChef / cookCleaner / janitorFarmerFirefighterCabin crewElectrician
Autonomous driving
Ride-hail / taxi driverTruck driverDelivery rider / courier
Majors
All majorsEnglish / Foreign languagesComputer scienceAccountingPsychologyJournalism / CommunicationFinanceLawVisual communication designMarketingNursingBusiness administrationEducation and teacher trainingArchitecturePublic administrationMedicineHospitality and tourism managementEconomicsInformation systems
Enter as:I have a jobI am studyingI run a companyI am building something
Recent changes›Security analyst (SOC)›2026-07-07
CapabilityCognitive automation2026-07-07

In a study with ten intrusion-detection experts, large models wrote network rules up to 90% syntactically valid, but the experts judged only 37.5% semantically correct and deployable

Security analyst (SOC)occupation page →
Event date / reported
2026-07-07
Evidence stage
CapabilityA demo, benchmark or paper shows the task can be done. Updates what the technology can do — not what employers will do.
Tasks this bears on
Writing the detection
Turning what you learned from one incident into a rule that catches the next one without drowning the queue.
Being augmented≈ Platform inference
Where this applies
University researchers generating network intrusion-detection rules with language models and putting them to ten domain experts. They report that large models achieved up to 90% syntactic validity, but the experts deemed only 37.5% of generated rules semantically correct and deployable, mainly because of insufficient specificity, heavy reliance on content matching and hallucinated logic; practitioners viewed the models as support tools for drafting and verification rather than independent generators, and small models were largely ineffective. It is a preprint with a small expert panel, in a laboratory setting.
What this means
Independent researchers found the same split as Microsoft did: models write rules that parse, and experts would deploy only about a third of them. Syntax is solved; knowing what the rule should catch is not.
What it does not yet show
A lab study with ten experts; it does not show what happens in a working security team or how rule quality changes over time.
What you can check
Open arXiv:2607.05916 ("Beyond the Syntax") and find "NIDS experts deem only 37.5% of generated rules semantically correct and deployable".
Does it change the assessment?
No — and this stage does not move it either. A "Capability" record is real evidence, but it does not upgrade a task judgement on its own. The 1 linked judgement above stand where they were.
Source
Lorenzo Di Filippo et al. (Sorbonne University, Sapienza University of Rome, TU Delft) — "Beyond the Syntax: Do Security Experts Trust LLMs for NIDS Rule Engineering?", arXiv:2607.05916v1 (7 July 2026, preprint) · verified 2026-09-28 · Claude (VOLO agent) · interpreted 2026-09-28 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for Security analyst (SOC) →All recent changes →How events become evidence →