Colombia · SFC · Circular Básica Jurídica
SFC Circular Básica Jurídica: evidence for vulnerability management and analysis
Colombia's Financial Superintendence (SFC) requires supervised entities to manage vulnerabilities in their internet-exposed platforms. Under the Circular Básica Jurídica, as reissued by External Circular 006 of 2025, banks and payment companies must also run a separate vulnerability-analysis system that compares each report with the previous one. Each row shows the clause, our part, what stays with your team, and what you can show your auditor.
SeguriScan, IntruForce's platform, monitors your external attack surface — the systems your company exposes to the internet — and finds company data exposed online, such as leaked work accounts, and look-alike domains imitating your brand. We produce dated evidence for the internet-facing part of these clauses.
External review only · Nothing to install · No active testing without your approval
Last checked against the official text: 20 November 2026. This page is not legal advice.
Who the Circular Básica Jurídica applies to
Part I, Title IV, Chapter V applies to all entities supervised by the SFC, with listed exceptions. The vulnerability-analysis rules (Part I, Title II, Chapter I, 2.3.7) apply to credit institutions, low-value payment system administrators, specialised electronic deposit and payment companies (SEDPE), and supervised entities whose clients place orders remotely, over the internet or on mobile devices. The rows below are the clauses SeguriScan supports.
SFC Circular Básica Jurídica requirement map
How to read the table
- We run the checkSeguriScan does the checking work the clause describes for internet-facing systems; you decide what is critical, fix what is found and sign off.
- We deliver partSeguriScan does the internet-facing part or supplies inputs; the rest stays with your team.
- Outside SeguriScanSeguriScan does not cover these — listed so you know where to look.
(report, Word and Excel) — a file you download and keep.(in SeguriScan) — shown in the platform, not a download.
| Requirement | Our part | Stays with you | What you can show your auditor |
|---|---|---|---|
| T. IV Ch. V 4.2.2Manage the vulnerabilities of internet-exposed platforms that support critical information assets | We run the checkSeguriScan finds internet-facing systems linked to your domains, checks them for known vulnerabilities, rechecks them regularly and confirms a fix with a retest when you request one | Choosing which assets are critical; fixing what is found | A dated report for every check (report, Word and Excel); each finding's history with dates (in SeguriScan) |
| T. II Ch. I 2.3.7–2.3.7.1A vulnerability-analysis system that is separate and independent from your production systems | We deliver partSeguriScan runs outside your network, apart from your production systems, and analyses the systems reachable from the internet | Analysis of internal systems; your auditor's view of whether the setup meets 2.3.7.1 | A dated report for every check (report, Word and Excel) |
| 2.3.7.2An automatic consolidated report at least twice a year; the last two years of reports available to the SFC | We deliver partSeguriScan produces a report automatically after every check | Keeping two years of reports; internal systems | Each dated report, downloaded and kept in your records |
| 2.3.7.4Differential analysis: compare each report with the previous one | We deliver partSeguriScan shows what appeared, disappeared or changed between any two checks, and which findings (security issues found in a check) are new, resolved or reopened | Internal systems; adding the comparison to your report file | Comparison of checks (in SeguriScan) |
| 2.3.7.5–2.3.7.6CVE-compatible tools that reference MITRE's CVE names (CVE: the public catalogue numbers of known vulnerabilities) | We deliver partSeguriScan matches each finding to its CVE identifier where one exists | Requirements for your internal tools | CVE identifier for each finding (in SeguriScan) |
| T. IV Ch. V 4.1.8Monitor websites, blogs and social networks to identify possible attacks against the entity | We deliver partSeguriScan lists look-alike domains that imitate your brand and work accounts of your domain found in leaked data, shown masked | Social networks and blogs | Look-alike domains and leaked accounts for each check (in SeguriScan) |
Outside SeguriScan SeguriScan does not cover these — listed so you know where to look: the vulnerability tests of the internet channel (Title II 2.3.4.9.2) and attack-simulation exercises for continuity tests (4.1.6), which your security partner or another qualified provider runs, while SeguriScan keeps dated records between them; awareness activities (3.1.4); security in software development (3.8); analysis of internal systems; continuous monitoring for unusual behaviour (4.2.3); event correlation (SIEM); a security operations centre; incident reporting to the SFC; monitoring of social networks and blogs.
Evidence for your SFC review
Evidence helps only when it has a date and shows what changed. Download each report and keep it in your own records: that is the record your auditor sees, and how you keep two years of reports at hand.
In the report (Word and Excel), a file you keep, for every check
- the check period and the report date
- the findings of that check
In SeguriScan, shown in the platform
- a one-page summary for leadership, ready to print
- the internet-facing systems you confirmed
- each finding's history: when it was found, status changes, and the retest that confirmed a fix
- a comparison of any two checks: what appeared, disappeared or changed
- CVE identifiers, look-alike domains and leaked work accounts
Questions about the SFC Circular
- Does SeguriScan make us compliant with the Circular Básica Jurídica?
- No. Compliance depends on your policies, internal controls and the SFC's review. SeguriScan produces dated evidence for the internet-facing part of 4.2.2, 2.3.7 and 4.1.8.
- Is SeguriScan the separate system 2.3.7.1 asks for?
- It can serve that role for your internet-facing systems: it runs outside your network, apart from your production systems. Your auditor makes the final call. Internal systems need their own analysis.
- How do we keep two years of reports for the SFC?
- Download each report after every check and keep it in your records. Every report states its check period, so the file shows exactly when each check ran. Systems you confirm are included from the next check.
- Do you submit anything to the SFC for us?
- No. Your entity submits its reports. We provide the reports and answer your team's questions about the findings.
- Are reports in Spanish?
- Yes. Reports and the SeguriScan interface are available in English and Spanish.
- Can we try it before we decide?
- Yes. Request a free SeguriScan pilot: we agree which systems it covers, and you review the results in SeguriScan. No obligation to proceed.
Start with a free SeguriScan pilot
Send your domain and a work email. We'll reply by email to agree which systems the pilot covers.
External review only · Nothing to install · No active testing without your approval
A conversation with our security team about how SeguriScan's records fit your audit file.
Referred by another company? Name it in the form and we'll route your request through them.
Already in a pilot through a partner? Check your latest report against the table above and take your questions to your partner.
Get started
Check your company against this map
Share your company's website and a work email to request a free SeguriScan pilot. We'll reply by email to agree which systems it covers; then compare the results with the requirement map above.
- Nothing to install
- No access to your internal network
- No active testing without your approval