Skip to content
DM11AI TRUST & IT RISK PROTECTION
AI TrustAI governance, ISO/IEC 42001 and AI risk
Governance, Risk & CompliancePCI DSS, ISO 27001, Central Bank, SOC 2 and LGPD
CybersecurityPentesting, SAST/DAST, phishing, cloud and forensics
Security OfficeCISO, DPO, Ethical Hacker and DevSecOps as a Service
Business ContinuityResilience, BIA, crisis management and Cyber Antifrágil®
ProductsStandardsServicesProposals
Self-assessmentsFree assessments with the result on screen, no sign-up required
ComparisonsISO 27001 vs SOC 2, LGPD vs GDPR, pentest vs vulnerability assessment
FAQA hundred answers on standards, deadlines and scope
Case Studies42 stories by segment and signed testimonials
About UsContact
PTES
Talk to an expert

Technology and service companies

The SOC 2 certification that unlocks your enterprise contracts

Your largest customers ask for SOC 2, an independent report on how secure your systems are, before they sign. DM11 gets your company ready to reach the audit with controls working and proof on hand, and to walk away with the report that closes the deal.

Scope my proposalTake the self-assessment

DM11 prepares your company. The SOC 2 report is issued by an independent audit firm. A rule of independence stops whoever builds the controls from auditing the same client.

Who runs the preparation

  • 17 years in governance, risk and compliance
  • In-house checklist mapping 288 controls
  • Data protection and privacy specialists
  • Experience with bank and Big Four audits

How it actually works

What you get when you “certify” your company under SOC 2

You get a document that answers your customers' security questions on its own: a report with your controls tested one by one by an independent auditor. The market calls it a certification and we understand the request, but the technical name is different, and it explains the format. It is an attestation report, issued by an independent, licensed audit firm under the standards of the American body that defines the format. Knowing that changes what you can expect to receive at the end.

It is a report, and people read it

The result is a document with five sections. Among them are the system description, written by your company, and the auditor's test results, control by control. Your customer will read it, especially the part that shows the problems found. It is not a one-page PDF with a logo.

The independent audit firm signs it

A consultancy does not sign SOC 2 reports, and neither do we. There is a rule of independence that explains why: whoever built the controls cannot audit the same client. That is why the independent audit is a separate stage, at a later moment. It comes in once your company has passed our pre-audit, or has carried out everything we recommended, and the contracting arrangement is something we settle in your case.

Type II looks at a period

The report most often requested does not assess how your company looks today: it assesses how it worked over months. Which means preparation does not end when a control is built, but when it has produced consistent proof across the whole period observed.

Without organized preparation

  • Contracts stuck in the customer's review, waiting on a report that takes months
  • Controls built in a rush, with no proof from the period the auditor will test
  • Scope guessed at, paying for categories the customer never asked for
  • Problems in the report nobody saw coming, showing up in front of the customer
  • Walking into the audit without knowing whether the controls will hold

With the house in order

  • Scope sized to what your customer actually needs
  • Proof being produced from the first day of the period observed
  • Problems caught by us, and fixed before the auditor arrives
  • A report that answers customers' security questionnaires on its own
  • The next cycle already prepared, with no uncovered gap between reports

The first decision

Type I and Type II

This choice sets cost, timeline and what you can actually show a customer. It is also where the market's most expensive misunderstanding circulates.

Type IA specific date

How the controls are designed

Checks whether the controls are well designed and in place on a given date. It is a snapshot. It shows you are serious quickly and often unblocks a contract while Type II is still under way. It says nothing about the controls having worked over time, and experienced buyers know that.

Type IIAn observation period

How they were designed and how they worked

Checks whether the controls were well designed and whether they actually worked over a period. It is the report most large customers require. The period is agreed between you and the auditor, and the market tends to treat three months as the minimum, with six to twelve months most accepted by demanding buyers.

The idea gets around that Type I is a prerequisite for Type II. It is not. Your company can go straight to Type II, and many do, to save time and a whole project. Doing Type I first is a commercial decision, and a good one: when a contract is waiting and you cannot sit out the observation period, it unlocks the signature.

Scope

One category is mandatory. You choose the other four.

Security, the group of common criteria, is in every SOC 2. The other four are eligible add-ons: you choose them based on what you already promise in contracts and what the market you sell to will demand. Eligible does not mean skippable. It is your call, and the call has an expiry date, because every category included later needs its own observation period. That is why the cheapest moment to include one is now, alongside the rest.

CategoryEligibilityWhy it is worth including
SecurityMandatoryThe group of common criteria, organized into nine blocks that run from the control environment to vendor management. It is the backbone of any SOC 2 report, and on its own already meets much of what customers ask for.
AvailabilityEligibleYou already promise availability in your contracts: the service level agreement (the SLA) is signed with or without SOC 2. This category is what proves the promise holds, covering capacity, recovery and testing of the plan. Leaving it out tends to last until the first renewal with a large account, which asks for exactly this.
ConfidentialityEligibleWorth it whenever a customer marks some information as confidential and expects to see it protected by agreement, which in practice is almost every enterprise contract. It covers identifying, keeping and disposing of that information. It is the category with the least extra effort for anyone who has done Security, because it reuses much of the same set of controls.
Processing integrityEligibleNeeded when your service processes a transaction or calculation on the customer's behalf and the result has to be complete, accurate and authorised. In payments, payroll, billing and logistics, it answers the question the customer really has: is the number coming out of here correct? Security alone does not answer that.
PrivacyEligibleIt comes in when you handle personal data, and buyers ask for it more and more as privacy law tightens. It covers part of what the law requires and does not replace a privacy program, but it shows the customer, backed by a third party, exactly the part they push hardest on when reviewing you.

The calculation people usually get wrong: adding a category in the next cycle does not cost a little more, it costs a whole observation period just for it, and until then you tell the customer it is not covered. It is worth asking the customer, in writing, what they expect to receive, and deciding the scope while also looking at the contracts you want to win over the next two years.

The real timeline

From the decision to the report in hand

The total timeline is almost never published, and it is exactly the one that matters when a contract is waiting. The phases below happen one after another, and it is the sum of them that you need to agree with your customer.

  1. 01

    Diagnosis and scope definition

    Comparing your situation with the criteria, defining categories, systems and environments, and the choice between Type I and Type II. It ends with a plan and the scope on paper.

  2. 02

    Fixes

    The phase with the least predictable length, and the biggest risk of blowing the timeline. It depends entirely on how much already exists. A company with governance in place moves fast; one that never formalised anything has groundwork to do.

  3. 03

    Observation period

    It only exists in Type II, and it is calendar time you cannot shorten. The controls have to work and produce proof across the whole period agreed with the auditor.

  4. 04

    Auditor fieldwork

    The independent audit firm tests the controls, examines the proof and talks to the team. This is where the difference shows up between the process on paper and the one done for real.

  5. 05

    Report delivery

    Writing, your company's response to any problems found, and delivery. The document comes out in English when the firm is American, which is usually the case.

We do not publish a standard timeline because it would be a guess: the fixes vary too much from one company to another, and the observation period is a scope choice. What can be said with confidence is that a Type II does not come out in weeks, because the observation period is calendar time you cannot shorten. After the diagnosis, we can put dates on your case precisely enough for you to commit to the customer.

Who does what

The split of roles, stated before you hire

A SOC 2 project involves four parties, each signing something different. We make the split clear before the proposal so there is no surprise about scope or fees later.

Your company
Writes the system description, a section of the report that management takes formal responsibility for, and signs the management assertion. It also hires the audit firm.
DM11
Prepares. Defines scope, runs the diagnosis against the criteria, builds controls, writes policies, sets up the proof routine, trains the team and runs the rehearsal before the audit. We do not sign the report and we are not an audit firm.
The independent audit firm
Signs the report. It comes in at a later stage, after the preparation, and for independence it cannot have built the controls it is going to test.
Your customer
Defines what they need to receive: which type of report, which categories and how often. It is worth getting that in writing before sizing anything.

Self-assessment

How close your company is to holding up under an audit

Eighteen questions across the control groups the report examines. The full result appears on screen, with a score per group and what closes the biggest gaps. We do not ask for your email to show it.

Control environmentQuestion 1 of 18

Is there a code of conduct communicated, with proof the team accepted it?

The report starts with the control environment, where the audit tests culture with a document in hand.

What each result means

The reading for each area, across the three result ranges. It is the same text emailed to those who identify themselves, published here for anyone who wants to understand what the score measures before answering.

Control environment

Below 50

With no written policy and no defined roles, the auditor has nowhere to start: they ask who approves what and hear three different answers. Begin with the minimum set of policies, dated approval, and proof they reached the team.

50 to 79

The policies exist and have aged. The auditor compares the text with practice, and the gap becomes an exception in the report. The cheapest work is rewriting what is already consensus and recording the approval again.

80 or above

A mature control environment. What usually goes missing here is evidence of continuity: proof that the review happened on the schedule the policy itself sets, not just once.

Information and communication

Below 50

Nothing the company decides about security reaches the people doing the work, and the auditor measures that by asking the team, not the leadership. A communication channel and a training record cover most of it.

50 to 79

Communication happens and leaves no trail. Without a record of who received what and when, the control exists but is not auditable, which for the report amounts to almost the same thing.

80 or above

Structured, recorded communication. Worth checking that the external channel, for customers and for whistleblowing, gets the same care as the internal one: that is where most companies find a gap.

Risk management

Below 50

Without a formal risk assessment, the rest of the report has no foundation: trust services criteria exist to treat risks, and the auditor asks which. Start with a simple inventory and a matrix that leadership approves.

50 to 79

The assessment exists and is not used. A risk identified with no treatment, no owner and no review is a parked document, and the auditor reads the last update date before reading the content.

80 or above

Live risk management. The thing to watch is the explicit link between risk and control: the report gets much stronger when each control names the risk it treats.

Monitoring

Below 50

Nobody checks whether controls keep working between audits, and that is exactly what a Type 2 examines. A simple routine of periodic verification already changes the outcome.

50 to 79

There is verification, without a defined cadence. The auditor looks for regularity: a control checked three times in nearby weeks and then forgotten for six months shows up as an operating failure.

80 or above

Monitoring with cadence. The next step is closing the loop: recording what the check found and what was done about it, not only that it happened.

Access

Below 50

This is the group that produces the most exceptions in a SOC 2 report. Without approved provisioning, deprovisioning on exit within a deadline and periodic review, the auditor is almost certain to find an active account for someone who left.

50 to 79

The process covers most systems, and some were left out. The auditor will ask for the full list of in-scope systems and check them one by one, including the ones IT does not administer.

80 or above

Mature access management. Check privileged and emergency access separately: they usually have their own rules, and that is where periodic review forgets to look.

Operations

Below 50

With no detection and no incident process, the company cannot prove it would notice a problem, which is what the security criterion asks. Start with log collection and a written response plan.

50 to 79

There are tools and no routine. Alerts nobody handles and vulnerabilities with no remediation deadline show up as a control designed but not operating, which is the worst category.

80 or above

Solid operations. What adds value now is evidence of timing: a record of when the alert appeared, when someone looked and when it closed.

Change management

Below 50

A production change with no approval and no record is a guaranteed finding. The auditor takes a sample of changes from the period and asks for the approval of each: with no trail, there is nothing to show.

50 to 79

The process exists and gets bypassed in emergencies. Emergency changes need their own path, with recorded after-the-fact approval, or they become the exception that brings down the whole control.

80 or above

Auditable change management. Worth checking that the separation between who develops and who deploys is enforced by permissions, not only by agreement.

Vendors

Below 50

Without third-party assessment, the company inherits the risk of whoever it hires and cannot demonstrate control over it. Start with the list of who touches customer data, which is usually shorter than expected.

50 to 79

There is an assessment at onboarding and nothing afterwards. The auditor asks about reassessment and about the SOC 2 reports of critical vendors, which is the evidence they most readily accept.

80 or above

A structured third-party programme. The detail that is often missing is the shared responsibility matrix with the cloud provider, documented and reviewed.

Availability

Below 50

If the availability criterion is in scope, backups and a recovery plan stop being good practice and become an obligation. Without a restore test, the backup does not count as a control.

50 to 79

Backups exist and there is no proof they come back. A restore test with a record of the date, the owner and the result is what turns a backup into evidence.

80 or above

Availability sustained. The next step is tying the recovery objective to the commitment in the customer contract, because that is the promise the report attests to.

Confidentiality

Below 50

With the confidentiality criterion in scope, you need to know where classified information sits and who can reach it. Without classification, there is no way to demonstrate proportionate protection.

50 to 79

Classification exists on paper and does not govern access. The auditor checks whether the retention and disposal rule is actually followed, and that is the part that usually falls short.

80 or above

Confidentiality handled well. Check disposal: classified information that should have been deleted and is still stored is the most common finding for this criterion.

Proof routine

Below 50

With no organised evidence, the audit turns into a weeks-long scramble for screenshots and spreadsheets, and the cost of the report rises with it. Start by defining where each piece of evidence lives and who produces it.

50 to 79

The evidence exists, scattered. Centralising it by control, with an owner and a frequency, is what separates a calm Type 2 from one that consumes the whole team.

80 or above

A mature proof routine, and it is what shortens the audit most. The next gain is automating collection of the repetitive parts, so evidence does not depend on someone remembering.

How we run it

From scope definition to the delivered report

Every phase ends with something delivered. You know what you get before you start.

  1. 01

    Define the scope

    We turn your customer's requirement into a report type, categories, systems and period. It is the decision that moves cost and timeline the most, and the one most often rushed.

    You get

    • Scope on paper with categories and systems
    • Type I or Type II decision with the reasons
    • Formal questions to send your customer
  2. 02

    Diagnosis against the criteria

    We assess where you stand today control by control, using the same checklist we use in audits, to show the real distance rather than an impression.

    You get

    • Diagnosis per control group
    • Gap report in order of priority
    • Effort estimate per front
  3. 03

    Fix

    We put in place, together with your team, what is missing: policies, access processes, changes, monitoring, incident response and vendor management.

    You get

    • Approved policies and procedures
    • Controls in place and working
    • Training for the areas involved
  4. 04

    Set up the proof routine

    In Type II the auditor tests the whole period, so the proof has to come out of day-to-day work. We define what is produced, by whom and how often, before the period starts.

    You get

    • Proof map per control
    • Routine with owners and a frequency
    • Repository organized for the audit
  5. 05

    Write the system description

    We help write the section of the report that is your company's responsibility, including the system boundaries, the commitments made and the role of the partners.

    You get

    • System description written
    • Boundaries and partners defined
    • Controls expected from the customer
  6. 06

    Rehearse and support

    We simulate the audit with the same rigor as the auditor before they arrive, and we support the independent audit firm's fieldwork, including your company's response if there is any problem.

    You get

    • Readiness report with what was found
    • Fixes made before the audit
    • Support during the fieldwork

Stories

Four situations we have already solved

We hide the clients' names with the same confidentiality that will protect your company later. The names change, and the pattern of the problems repeats.

Software as a service

The contract that could not wait for the period

Situation
A corporate customer made signing conditional on a SOC 2, with a two month deadline. The company had nothing formalised, and the most requested report needs an observation period that did not fit that window.
What we did
We went to the customer together with the company and proposed a two-step path: Type I on the date that was possible, with a dated commitment to Type II right after. At the same time, the fixes began, already producing proof for the next period.
Outcome
The contract was signed on the Type I. The Type II observation period started with the controls already working, instead of starting from zero later.
Fintech

Good technology and no trail

Situation
Engineering was mature: code review, separated environments, monitoring. But none of it left a record that could hold up in an audit test. Changes went to production with verbal approval in chat.
What we did
Rather than creating a new process, we adjusted what the team already used so the trail came about on its own: approval recorded in the development tool itself and access proof pulled automatically.
Outcome
The team did not change its routine and the audit got something to test. The internal argument about bureaucracy, which usually stalls these projects, never even happened.
Data platform

Chose scope by whichever customer was asking

Situation
The company was about to hire only Security, because that was what the customer who prompted the project had asked for. Its own contract, though, promised availability with a service level agreement, and half the pipeline was large accounts that audit their vendors.
What we did
We read the signed contracts before settling the scope, and not just that one customer's request. Availability went into the same observation period, alongside Security. Processing integrity stayed out with a written justification, because the company does not process calculations on anyone's behalf.
Outcome
The report came out covering what the contract already promised. When the availability requirement came up in a later negotiation, the answer was already ready, instead of costing a new observation period just for that category.
Infrastructure provider

Found out about the problems in front of the customer

Situation
In the first cycle, with no rehearsal beforehand, the report came out with problems the company had not expected, including active access for people who had already left. The document went to the customer with those problems on display.
What we did
In the next cycle we added a rehearsal run with the same rigor as the auditor, months before the fieldwork. The problems appeared to us first, with time to fix them and to produce proof of the fix.
Outcome
The next report came out without the earlier problems. The lesson that stuck was a different one: a problem is not a catastrophe, but finding out about it together with the customer is avoidable.

Scoping

Build the scope of your proposal

Twelve questions about what sets the size of a SOC 2 project. At the end you review your answers, correct anything you want, and get a proposal built on that, without needing a meeting just to find out the basics.

ReportQuestion 1 of 12

Which report did your customer ask for?

If the request does not say, it is worth confirming before pricing.

Frequently asked

What people ask before deciding

Answers based on the standards of the AICPA (the accountants' body in the United States). Where no official figure exists, we say so.

You can, and almost everyone does. When your customer asks for a SOC 2 certification, we know exactly what they want. The technical name, though, is an attestation report, issued under the standards of the American Institute of Certified Public Accountants (the accountants' body in the United States), and the difference matters on three practical points. Who signs it: only an independent, licensed audit firm, never a consultancy. What you receive: a report of several sections that the customer will read, including the tests control by control, and not a one-page certificate. And the timeline: because the most requested report covers a period of working, it does not shorten the way a traditional certification audit does. Knowing this changes what you hire and from whom.

No, and no consultancy does. The report is issued by an independent, licensed audit firm. There is a rule of independence that reinforces the separation: whoever built the controls cannot audit the same client. We prepare your company and support the fieldwork, and the audit comes in at a later stage, once you are ready to pass.

No. This is a common and expensive misunderstanding, because it leads companies to buy an extra project. You can go straight to Type II, and many companies do. Type I makes sense when a contract is waiting and you cannot sit out the observation period: it unblocks the commercial conversation while Type II matures. It is a business decision, not a requirement of the standard.

Type I checks whether the controls are well designed and in place on a specific date. It is a snapshot. Type II checks whether they were well designed and whether they actually worked over a period. Type II is what most large customers require, precisely because a control can be well designed and still not work in practice. The period is agreed between you and the auditor, and the market tends to treat three months as the minimum, with six to twelve months most accepted by demanding buyers.

It depends on two things that only become clear in the diagnosis: how much already exists, which drives how long the fixes take, and which observation period you adopt. We do not publish a standard timeline because it would be a guess. What can be said is that a Type II does not come out in weeks, because the observation period is calendar time you cannot shorten. If your customer's deadline is short, there is a path: Type I unlocks the signature while Type II matures. After the diagnosis, we can put dates on your case.

Only Security, the group of common criteria, is mandatory. Availability, Confidentiality, Processing integrity and Privacy are optional: you choose them based on what you promise in contracts and what your market demands. Decide carefully, because the choice has a clock on it: a category added later needs an observation period of its own, and until the next report comes out you tell the customer it is not covered. In practice, anyone selling software with a service level agreement almost always needs Availability, anyone processing a transaction on the customer's behalf needs Processing integrity, and Confidentiality tends to be the one with the least extra effort, because it reuses the Security controls. In the diagnosis we look at your signed contracts, and not just the request from the customer of the moment.

A great deal, and the project genuinely shrinks. Much of the policies, the access controls, the vendor management and the governance structure serves both. The main difference is not in the controls, it is in what each one assesses: ISO certifies the management system, while SOC 2 attests how the controls worked over a period. In practice that means the routine of producing proof the whole time tends to be the biggest gap for those coming from ISO, along with the system description, which has no equivalent in the standard.

No, though it helps a lot. The Privacy category covers part of what privacy law requires, and the report can serve as proof of the technical and administrative measures the law asks for. But it does not replace records of processing, the definition of a lawful basis, handling data subject requests or a data protection officer. They complete each other: a company that has already organized its privacy program arrives with an advantage in SOC 2, and the reverse holds too.

A flagged problem is not a failure, and this is the biggest confusion for those who come to SOC 2 expecting a pass-or-fail result. Reports carry these problems often. What matters is the auditor's opinion, which can be without reservation or with reservation, and your company's response to each point. A report with one well-described problem, with its cause and a plan to fix it, is still a document that wins deals. What alarms a customer is a problem with no explanation, or a pattern of problems repeating from one cycle to the next. That is why we run a rehearsal before the auditor arrives: so the problems appear to you first.

It is the letter your company issues to cover the gap between the end of the last report's period and the date a customer is reviewing you. Because the report covers a past period, there is always an uncovered window, and customers reviewing you ask about it. The letter states that nothing relevant changed in the controls during that gap. It is your document, not the auditor's, and it is the most common practical question from those who already hold the report and get a review outside the cycle.

They are the controls your report will list as the responsibility of whoever hires you. No service works on its own: if your customer sets up the permissions inside your product badly, the control fails on their side, and the report has to say so. Defining that list well protects you and avoids an argument after an incident. From the other side, when it is your company reading a supplier's SOC 2, that is exactly the section that says what is still left for you to do, and almost nobody reads it.

Yes, and this is where a lot of people are surprised. SOC 2 Type II is a continuous routine, not a project with an end. The next report has to cover the period right after, with no hole left, otherwise the customer asks what happened in the months left out. The second cycle usually takes less work than the first, because the structure already exists, but it is not zero: what weighs is producing proof across the whole year, and not the audit itself.

SOC 1 deals with controls that affect customers' financial statements, and is usually asked for by those who have a financial audit involved. SOC 2 deals with security and the other categories of trust, and is the most common request from technology customers. SOC 3 is a public, summarized version of SOC 2, without the test details, which can go on your website without a confidentiality agreement. If your customer only asked for a SOC, it is worth confirming which one, because they are different projects.

It is confidential and circulates under a confidentiality agreement, so it does not go on your website. The practical use is answering the customers' reviews: instead of filling in a different security questionnaire for each one, you hand over the report and the conversation gets shorter. It also backs up a contract clause and tends to speed up the sale to large accounts. If you want something public, the way is SOC 3.

Usually yes, because the firm that signs tends to be American and the document follows the AICPA standards. This is rarely a problem, since whoever requires the report is generally a customer or investor from abroad. The preparation, the internal documentation and the policies can be in Portuguese, and we work in both languages.

More questions? Talk to DM11

Your SOC 2 certification, sized to what the customer actually requires

A thirty minute conversation is usually enough to settle report type, categories and a rough idea of the effort involved. No obligation.

Talk to a specialistBuild the scope now

Comparisons on this subject

  • SOC 2 vs ISO 27001
  • SOC 2 Type 1 vs Type 2
  • ISO 27001 vs NIST CSF
See all 13 comparisons

Sources and references

  • System and Organization Controls (SOC) suite of services

    AICPA, instituto americano dos contadores públicos certificados · accessed on July 28, 2026

  • Information security, cybersecurity and privacy protection — Information security management systems — Requirements

    ISO/IEC · ISO/IEC 27001:2022, edição 3, com a emenda 1:2024 · accessed on August 10, 2026

Published on
July 24, 2026
Last reviewed on
August 01, 2026
Editorial review
DM11 Consultoria em Segurança da Informação Ltda

This page is informational and describes how DM11 reads and applies the sources above. It does not reproduce the text of any standard, does not replace reading the official document, and does not replace an audit, a certification, an independent assessment or legal advice. Where a standard requires formal assessment, it is carried out by an accredited body, auditor or assessor, always separate from whoever did the preparation.

DM11AI TRUST & IT RISK PROTECTION

ouvir. entender. resolver.

Trust to grow in the AI era. AI governance, IT risk and compliance, cybersecurity and business continuity for companies that cannot stop.

Solutions

  • AI Trust
  • Governance, Risk & Compliance
  • Cybersecurity
  • Security Office
  • Business Continuity

Products

  • oitenta20®
  • Jigphish®
  • Ethical Hacker as a Service
  • DPO Backoffice®
  • SastAction®
  • NosConformes®
  • Cyber Antifrágil®
  • All products

Company

  • About Us
  • Case Studies
  • FAQ
  • Contact

Contact

  • contato@dm11.com.br
  • +55 (11) 4837-5758
  • Av. Eng. Luís Carlos Berrini, 1140, 7º andar, Brooklin, São Paulo/SP, CEP 04571-000
  • Standards and certifications
  • Comparisons between standards
  • Self-assessments
  • Services
  • Request a proposal

DM11 © 2026 · All rights reserved.

  • Privacy Policy
  • Cookies
  • Terms of use
  • Ethics and conduct
  • Anti-corruption
  • Social responsibility