SecOraLens

Methodology

How SecOraLens sources and verifies advisories

SecOraLens turns security advisories into plain-language briefs and short videos for SOC analysts and security leaders. We do not replace original security research: every advisory on this site credits its source and links to it, so you can always read the original before you act.

Where advisories come from

We monitor 18 public sources — vendor and research blogs, security news outlets and government catalogues — checking for new items about every hour:

How an advisory reaches the site

  1. Collected. New items are pulled from the sources above and de-duplicated.
  2. Classified. Each item gets a severity and a category (vulnerability or threat) from signals in the source.
  3. Checked for relevance. Items must read as genuine security advisories; opinion, marketing and policy posts are filtered out.
  4. Published. High- and critical-severity items that pass these checks are published automatically with the source's own summary and a link to the original; other items may be reviewed by an analyst first.
  5. Explained. The most important advisories also get a short video briefing.

How we use AI — and how it is checked

We use AI to help summarise source articles and to draft the scripts for our video briefings. Because AI can make mistakes, the facts shown under “Key details” on an advisory page are checked automatically against the source article: each point must be backed by an exact quote from it, and every CVE identifier and number must appear in the source text, otherwise it is dropped. We never state that a flaw is being exploited unless the source says so — the one exception is a flag for vulnerabilities listed in CISA's Known Exploited Vulnerabilities catalogue, which is defined by that catalogue itself. Our scripts are generated from the advisory's own data and instructed not to invent CVE numbers, malware names, threat actors or statistics.

Dates and updates

The date shown on an advisory is the date its original source published it, not the date we processed it. Where a source gives no date, we show none.

Corrections

If you find an error, or you are a researcher or vendor and want a credit or a link corrected, email intel@secoralens.com with the advisory link and what should change. We correct or remove inaccurate content.

Limits

Advisories on SecOraLens are for information. They are not a substitute for your vendor's official guidance or for your own assessment of your environment — always confirm affected versions and fixes with the original source.

Browse the latest advisories, learn why SecOraLens exists, or contact us.