What a Fractional CTO Actually Reviews in the First 30 Days
NIST's own framework starts with an inventory most platforms have never actually produced. A fractional CTO's first 30 days is built around producing it.

- NIST's Cybersecurity Framework 2.0 opens with the Identify function, which requires maintained inventories of hardware, software, services, data, and network data flows before anything else in the framework can function. A fractional CTO's first 30 days is built around producing exactly this inventory, because most platforms have never actually assembled it.
- The same Identify function requires a risk assessment that records vulnerabilities, threats, and the likelihood and impact of each one, plus an assessment of critical suppliers before they are even engaged. A platform that has never done this has no documented basis for any security decision it has made to date.
- PCI DSS Requirement 12.5.2 requires documenting and confirming PCI DSS scope at least once every 12 months, a requirement effective immediately under v4.0. A fractional CTO's first question is often simply when this was last done, because a platform that cannot answer has already failed the requirement regardless of how good its actual security posture is.
- Service providers face a stricter version under Requirement 12.5.2.1: scope has to be documented and confirmed at least every six months. A platform that classifies itself as a service provider and is still running on an annual cycle is out of compliance on timing alone.
What a fractional CTO actually reviews in the first 30 days starts with a question most founders cannot answer on the spot: what does the platform’s own infrastructure, data, and vendor footprint actually consist of, documented and current, rather than remembered. NIST’s Cybersecurity Framework 2.0 puts exactly this question first, before any other security function in the framework can meaningfully operate. A fractional CTO’s early weeks are built around producing that answer, because most growing platforms have simply never assembled it.
Why the inventory comes before anything else
NIST’s Cybersecurity Framework 2.0 organizes its core functions starting with Identify, defined as the function where an organization’s current cybersecurity risks are actually understood. The Asset Management category inside Identify is specific about what that understanding requires in practice. Inventories of hardware managed by the organization have to be maintained. Inventories of software, services, and systems have to be maintained separately. Representations of the organization’s authorized network communication and both internal and external data flows have to be maintained. Inventories of services provided by suppliers have to be maintained as their own category, distinct from the organization’s own systems.
A platform that has grown quickly rarely has any of this assembled in one place. Different pieces exist in different people’s heads, a cloud console here, a vendor contract folder there, a Slack thread explaining why a particular integration exists. A fractional CTO’s first 30 days is not spent making technical decisions yet. It is spent building the actual inventory NIST’s framework treats as the precondition for making any security decision credibly at all. Decisions made before this inventory exists are decisions made without knowing what is actually being protected.
Why the risk assessment has to follow, not precede, the inventory
The same Identify function requires a risk assessment, and NIST’s framework is specific about what belongs in it. Vulnerabilities in assets have to be identified, validated, and recorded. Internal and external threats have to be identified and recorded separately. The potential impacts and likelihoods of threats actually exploiting those vulnerabilities have to be identified and recorded, and that combination of threat, vulnerability, likelihood, and impact is what should inform how risk responses actually get prioritized.
This ordering matters for how a fractional CTO’s first month is actually structured. A risk assessment performed before the asset inventory exists is assessing risk against an incomplete picture of what is even there to assess. A fractional CTO who starts proposing specific security fixes in week one, before the inventory is actually done, is working from the same incomplete picture every previous ad hoc security decision was made from. The sequence is not bureaucratic caution. It is the only way the second step actually produces a result worth trusting.
Why critical suppliers get checked before anything else happens with them
NIST’s framework adds a detail that applies directly to a payments platform’s vendor-heavy architecture. Critical suppliers are specifically called out as something to be assessed prior to acquisition, not after a relationship is already running. A fractional CTO reviewing an existing platform is usually looking at this backwards from how the framework describes it: vendors already integrated, contracts already signed, and no documented assessment of which of those vendors are actually critical to the platform’s operation or what risk each one specifically introduces.
Part of the first 30 days is reconstructing that assessment after the fact, ranking existing vendors by how critical they actually are to the platform’s operation, not by how long they have been in place or how large their invoice happens to be. A payment gateway the entire platform depends on and a minor analytics tool a few people glance at occasionally are not the same category of risk, even if both showed up on the vendor list the same way. Sorting that out is part of the inventory work, not a separate exercise that happens later.
Why the review does not stop at a single snapshot
NIST’s framework adds a fourth category inside Identify that is easy to treat as an afterthought: Improvement. It covers identifying improvements from evaluations, from security tests and exercises run with suppliers and other third parties, from the actual execution of operational processes, and from incident response plans themselves being established, communicated, maintained, and improved over time. This category exists because an inventory and a risk assessment produced once, then left alone, go stale at exactly the rate the business keeps changing underneath them.
A fractional CTO’s first 30 days produces a snapshot. What makes that snapshot useful past the first quarter is building the mechanism that updates it: a defined cadence for re-running the inventory, a trigger for reassessing risk when a new vendor comes on or an existing one changes its own posture, and a documented path for feeding lessons from an actual incident back into the plans that are supposed to prevent the next one. A platform that treats the first 30 days as a one-time project, rather than the start of a recurring process, ends up back in the same undocumented state within a year, just with a dustier PDF to point to in the meantime.
The specific, dated question most platforms cannot answer
Alongside the general framework review, a fractional CTO at a payments platform specifically has one narrow, specific question to ask early, because the answer is either compliant or it is not, with no middle ground. PCI DSS Requirement 12.5.2 requires that PCI DSS scope be documented and confirmed at least once every 12 months, and the requirement has been effective immediately since PCI DSS version 4.0 took effect. A platform that cannot produce the date of its last scope documentation, or has never produced one at all, has already failed this specific requirement, independent of how strong its actual technical controls happen to be elsewhere.
The requirement goes further for a specific category of business. Requirement 12.5.2.1 requires service providers specifically to document and confirm scope at least once every six months, twice the frequency a standard merchant faces under 12.5.2. A platform processing or storing cardholder data on behalf of other businesses, rather than solely for its own transactions, needs to confirm which category it actually falls into. A platform assuming the annual cycle applies, when it actually meets the service provider definition, is out of compliance on timing alone, well before anyone examines whether the scope documentation itself is any good.
A concrete example: the platform that had security but not an inventory
Picture a payments platform that has genuinely invested in security over several years. Individual engineers know their own services well. Access controls exist. Nobody would describe the engineering culture as careless. What nobody has ever produced is a single, current document listing every system, every data store, every third-party service touching cardholder data, and every vendor the platform actually depends on.
A fractional CTO’s first 30 days at this platform does not find the security posture weak. It finds the security posture undocumented in exactly the form every framework and every standard actually requires it to be documented. The platform cannot answer when PCI scope was last confirmed, because nobody has ever run that exercise formally. It cannot produce a ranked list of critical suppliers, because supplier risk was never assessed as its own category separate from simply onboarding a new vendor when a need arose. Nobody can say with confidence which of the platform’s dozen or so third-party integrations actually touch cardholder data and which only ever see anonymized reporting figures, because that distinction was never mapped out as a deliberate exercise.
None of this means the platform was insecure. It means the platform could not prove what it actually knew, to an assessor, an investor, or a sponsor bank’s own review, because the proof NIST’s framework and PCI DSS both require was never assembled. A sponsor bank’s own periodic review, or an investor’s technical diligence ahead of a funding round, asks for exactly these artifacts. Discovering the gap during that conversation, rather than before it, turns a routine review into a scramble that a thirty-day engagement, run proactively, was built specifically to prevent.
What the first 30 days actually produces
The deliverable from a fractional CTO’s opening month is not a list of recommended fixes yet. It is the inventory, the risk assessment built on top of it, the ranked supplier list, and the specific answer to when PCI scope was last documented and confirmed, with a plan to bring that cadence into compliance going forward. Everything that follows, architecture decisions, vendor renegotiations, security investment priorities, depends on this foundation existing first. Skipping ahead to recommendations without it produces exactly the kind of undocumented, ad hoc security posture the platform was likely already running before the fractional CTO arrived.
Building that foundation correctly in the first 30 days, rather than guessing at priorities before the actual picture exists, is exactly the discipline behind Midcore’s fractional CTO engagements. Where the gap turns out to be broader than one role can close alone, a business operations audit is built to surface exactly which parts of the business have never been formally documented at all. And once the inventory and scope work is done, multi-cloud security and compliance work is where that documentation gets turned into the evidence an assessor or a sponsor bank actually wants to see.
Frequently Asked Questions
What is the first thing a fractional CTO actually does when starting at a payments platform?
Build or validate an inventory of what actually exists: hardware, software, services, data, and the network paths connecting them. NIST’s Cybersecurity Framework 2.0 names this specifically as the Identify function’s Asset Management category, and treats it as the foundation every other security activity depends on. Most growing platforms have never assembled this inventory formally, which makes it the first concrete deliverable a fractional CTO produces, not a preliminary step before the real work starts.
Why does a fractional CTO ask when PCI DSS scope was last documented?
Because PCI DSS Requirement 12.5.2 requires documenting and confirming PCI DSS scope at least once every 12 months, a requirement that has been effective since PCI DSS v4.0 took effect. If a platform cannot say when this was last done, or has never done it at all, that is an immediate, specific compliance gap, independent of how strong the platform’s actual technical security happens to be.
Does the scope documentation requirement apply differently to a platform that is a service provider?
Yes. Requirement 12.5.2.1 requires service providers to document and confirm PCI DSS scope at least once every six months, twice the frequency required of a standard merchant under 12.5.2. A platform that processes or stores payment data on behalf of other businesses, rather than purely for its own transactions, needs to check which category it actually falls into before assuming the annual cycle applies to it.
Sources: NIST Cybersecurity Framework 2.0, the Identify function, and PCI Security Standards Council, Summary of Changes from PCI DSS Version 3.2.1 to 4.0, Requirements 12.5.2 and 12.5.2.1.