CMMC Compliance Guide 2026 What DoD Contractors Need to Know
The Cybersecurity Maturity Model Certification (CMMC) is the Department of Defense's mandatory framework for protecting Controlled Unclassified Information in the defense industrial base. This guide covers everything a defense contractor needs to understand about CMMC 2.0: which level applies to your contracts, what the 110 Level 2 controls actually require, how the certification process works from gap assessment through C3PAO audit, what the timeline and cost look like, and what the most common compliance failures are so you can avoid them. Published by Petronella Technology Group, a CMMC Registered Practitioner Organization (RPO) based in Raleigh, NC.
Guide Contents
- What Is CMMC and Why Does It Exist
- CMMC and the DFARS Clause Framework
- CMMC Level 1, Level 2, and Level 3 Explained
- The 110 Practices of CMMC Level 2: All 14 Domains
- How CMMC Certification Works: C3PAO, RPO, and Assessor Roles
- CMMC 2.0 Phased Rollout Timeline
- POA&M Rules and Conditional CMMC Status
- What CMMC Compliance Costs
- Common CMMC Compliance Failures
- Frequently Asked Questions
1. What Is CMMC and Why Does It Exist
CMMC stands for Cybersecurity Maturity Model Certification. It is a Department of Defense program that requires defense contractors and subcontractors to verify their cybersecurity practices through assessment rather than simple self-attestation. The DoD launched CMMC in response to years of evidence that defense contractors were claiming compliance with existing requirements such as DFARS 252.204-7012 without actually implementing the required controls. Nation-state adversaries, particularly those affiliated with China and Russia, exploited these gaps to steal controlled technical data and intellectual property from the defense industrial base.
CMMC 2.0, the current version as of 2026, was published in the Federal Register in December 2024. It simplified the original five-level model to three levels and aligned Level 2 directly with NIST SP 800-171 Revision 2 (110 controls) rather than introducing a separate control set. Level 3 adds selected controls from NIST SP 800-172. The final rule means CMMC requirements can now appear in DoD solicitations and contracts.
Key Terms
- CUI (Controlled Unclassified Information): Federal information requiring safeguarding per Executive Order 13556. If your contract involves CUI, CMMC Level 2 applies.
- FCI (Federal Contract Information): Information provided or generated under a federal contract that is not public. FCI triggers Level 1.
- CMMC 2.0: The current rule, effective December 16, 2024. Three levels instead of five. Self-assessment permitted at Level 1; third-party C3PAO assessment required at Level 2 (most contracts).
- DIB (Defense Industrial Base): The network of companies that provide goods and services to the DoD. CMMC applies to every company in the DIB that handles FCI or CUI.
- SPRS (Supplier Performance Risk System): The DoD portal where contractors post their self-assessed NIST 800-171 score (used at Level 1 and during Level 2 preparation).
2. CMMC and the DFARS Clause Framework
CMMC does not replace the existing DFARS cybersecurity clauses; it adds a verification layer on top of them. Understanding which clauses apply to your contracts is the first step in determining your CMMC obligations.
| DFARS Clause | What It Requires | Who It Applies To |
|---|---|---|
| 252.204-7012 | Safeguard covered defense information per NIST 800-171; report cyber incidents to DoD within 72 hours; provide media to DoD upon request | Any contractor handling covered defense information (CDI/CUI) |
| 252.204-7019 | Conduct and document a self-assessment against NIST 800-171; post score to SPRS; provide assessment results to contracting officer on request | Contractors subject to 7012 who submit offers or bid on new contracts |
| 252.204-7020 | Allow DoD and its representatives to access systems, assessments, and documentation related to NIST 800-171 compliance | Same as 7019 |
| 252.204-7021 | Have a CMMC certificate at the level specified in the contract; maintain that level; flow down to subcontractors | Contractors when CMMC is specified in the solicitation (phased in 2025 onward) |
When DFARS 252.204-7021 appears in a contract or solicitation, your company must hold a valid CMMC certificate at the specified level before award. This is the enforcement mechanism that makes CMMC real. Once your prime contract requires CMMC Level 2, you must also ensure any subcontractors handling CUI on your behalf achieve the same level.
For a deeper look at the underlying control standard, see our guide to NIST SP 800-171 compliance.
3. CMMC Level 1, Level 2, and Level 3 Explained
CMMC 2.0 has three levels. The level required for a specific contract is determined by the type of information involved and the sensitivity of the program. Most defense contractors pursuing any CUI-bearing contract need Level 2.
15 Practices
Covers basic safeguarding of Federal Contract Information (FCI). Practices come from FAR clause 52.204-21. Annual self-assessment, no third-party required. Senior official annual affirmation to DoD required. Most simple product/service suppliers with no CUI fall here.
- Annual SPRS submission
- Self-assessment only
- No POA&M required
110 Practices
Covers protection of Controlled Unclassified Information (CUI). All 110 practices from NIST SP 800-171 Rev 2. C3PAO assessment required for most programs. Triennial reassessment. Annual senior official affirmation. This is the level that applies to the vast majority of defense supply chain companies handling any CUI.
- Third-party C3PAO assessment
- POA&M permitted (with conditions)
- Triennial reassessment + annual affirmation
110+ Practices
Adds select practices from NIST SP 800-172 beyond Level 2. Intended for contractors on the most critical DoD programs, where nation-state APT threat is highest. Government-led assessment by the Defense Contract Management Agency (DCMA). Relatively few contractors will need this level.
- DCMA government assessment
- Builds on Level 2 C3PAO certification
- Select 800-172 enhanced practices
Determining which level applies requires reading the specific DFARS clauses and any CMMC requirements listed in the solicitation or contract. When in doubt, contact the contracting officer or consult a CMMC Registered Practitioner.
4. The 110 Practices of CMMC Level 2: All 14 Domains
CMMC Level 2 maps directly to the 110 security requirements in NIST SP 800-171 Rev 2. These requirements are organized into 14 security domains (referred to as "families" in the NIST publication). Every requirement in every domain must be implemented and documented. Below is a brief summary of each domain and what it covers.
Access Control
Limit system access to authorized users, processes, and devices. Control the flow of CUI. Separate duties of users. Employ least privilege. Use non-privileged accounts for non-privileged activities. Prevent non-privileged users from executing privileged functions.
Awareness and Training
Ensure all users are aware of security risks. Provide role-based security training before authorizing access. Document training completion. This domain is frequently underestimated. Generic KnowBe4-style awareness training does not meet the AT-3 requirement for role-specific training.
Audit and Accountability
Create and retain system audit logs. Review and analyze logs for indicators of compromise. Protect audit logs from unauthorized access, modification, or deletion. Synchronize clocks of systems that generate audit records. Report audit failures promptly.
Configuration Management
Establish and maintain baseline configurations for systems. Establish and enforce security configuration settings. Track, review, approve, and log changes to systems. Analyze security impact of changes. Restrict, disable, or prevent use of nonessential programs, functions, ports, protocols, and services.
Identification and Authentication
Identify and authenticate users, processes, and devices before allowing access to systems. Enforce minimum password complexity. Prohibit password reuse. Employ multifactor authentication (MFA) for local access, network access, and remote access to privileged accounts. Use FIPS-validated cryptographic modules.
Incident Response
Establish an operational incident-handling capability. Track, document, and report incidents to officials. Test the incident response capability. Cyber incidents affecting CUI or covered defense information must also be reported to the DoD via the DIBNet portal within 72 hours.
Maintenance
Perform system maintenance in a controlled manner. Provide controls on tools, techniques, and personnel used in system maintenance. Ensure maintenance is performed only by authorized individuals. When maintenance is performed remotely, employ authenticators and encrypted channels.
Media Protection
Protect CUI on media containing CUI during transport and storage. Sanitize or destroy media before disposal or reuse using NIST SP 800-88 methods. Mark media containing CUI. Control access to media containing CUI. Implement cryptographic mechanisms to protect CUI on portable devices.
Physical Protection
Limit physical access to systems, equipment, and facilities to authorized users. Escort visitors, monitor visitor activity, and maintain visitor logs. Control and manage physical access devices. Protect and monitor facilities and supporting infrastructure. Protect CUI during transport.
Personnel Security
Screen individuals prior to authorizing access to organizational systems. Ensure CUI is protected during and after personnel actions such as terminations and transfers. Terminate accounts and revoke credentials within defined timeframes.
Risk Assessment
Periodically assess risk to operations, assets, and individuals. Scan for vulnerabilities in systems periodically and when new vulnerabilities are identified. Remediate vulnerabilities in accordance with risk assessments. Update inventories of CUI regularly.
Security Assessment
Periodically assess security controls in systems to determine if the controls are effective. Develop and implement plans of action to correct deficiencies. Monitor controls on an ongoing basis. Develop, document, and periodically update system security plans (SSPs).
System and Communications Protection
Monitor, control, and protect communications at external and internal boundaries. Employ architectural designs and engineering approaches that promote effective security. Implement subnetworks for publicly accessible system components. Deny network communications traffic by default. Employ FIPS-validated cryptography for CUI in transit and at rest.
System and Information Integrity
Identify, report, and correct system flaws in a timely manner. Provide protection from malicious code. Perform periodic scans and real-time scans of files from external sources. Monitor systems to detect attacks and indicators of potential attacks. Receive alerts when unusual or suspicious activity is detected.
The full text of all 110 requirements is in NIST SP 800-171 Rev 2, available at nvlpubs.nist.gov. The DoD's official CMMC assessment guides (CAPs) at dodcio.defense.gov provide the specific assessment objectives assessors use to evaluate each practice.
5. How CMMC Certification Works: C3PAO, RPO, and Assessor Roles
CMMC Level 2 certification requires a formal assessment conducted by an authorized third-party organization. The ecosystem involves several types of accredited entities with distinct roles. Understanding who does what prevents contractors from paying for the wrong type of service.
CMMC Third-Party Assessment Organization (C3PAO)
A C3PAO is a company authorized by the Cyber AB (CMMC Accreditation Body) to conduct official CMMC Level 2 assessments. When your assessment is complete and you pass, the C3PAO submits your results to the CMMC Enterprise Mission Assurance Support Service (eMASS), which generates your certificate stored in the Supplier Performance Risk System (SPRS). Only a C3PAO can issue a CMMC Level 2 certificate. A list of authorized C3PAOs is maintained at cyberab.org/marketplace.
Registered Practitioner Organization (RPO)
An RPO like Petronella Technology Group is authorized to provide CMMC advisory services, gap assessments, remediation support, SSP authoring, and readiness preparation. An RPO works with a contractor to get them ready for the C3PAO assessment. An RPO cannot conduct the official assessment or issue a certificate. This separation is by design: the entity that prepares you cannot be the entity that certifies you.
Registered Practitioner (RP)
An RP is an individual certified by the Cyber AB to provide CMMC advisory services within an RPO. Petronella Technology Group's team includes Craig Petronella (CMMC-RP), Blake Rea (CMMC-RP), Justin Summers (CMMC-RP), and Jonathan Wood (CMMC-RP). When working with an RPO, look for named RPs on deliverables.
CMMC Certified Assessor (CCA) and Lead Assessor (CCLA)
CCAs and CCLAs are individuals who work for or contract with C3PAOs to conduct the official assessments. They must pass Cyber AB certification and maintain their credentials. You will interact with CCAs during your C3PAO assessment.
What the Assessment Process Looks Like
A Level 2 C3PAO assessment typically follows this sequence:
- Pre-assessment scoping: The C3PAO reviews your SSP and scoping documentation to understand your CUI environment and confirm which systems are in scope.
- Document review: Assessors review your policies, procedures, SSP, POA&M, system inventories, and configuration documentation.
- Interviews: Assessors interview system administrators, security personnel, and end users to verify that documented practices match actual behavior.
- Technical testing: Assessors examine system configurations, log samples, network diagrams, MFA setups, and encryption implementations.
- Finding discussion: The assessor team reviews findings with your team before finalizing. You can provide additional evidence for items initially marked as not met.
- Final report and submission: The C3PAO submits results to eMASS. If you pass, your CMMC certificate is created in SPRS. If deficiencies remain, you may pursue conditional CMMC status with an approved POA&M.
For a detailed look at what our readiness work includes before the C3PAO assessment, see our CMMC consulting and readiness services page.
6. CMMC 2.0 Phased Rollout Timeline
CMMC requirements are being phased into DoD solicitations and contracts incrementally, not all at once. The final rule went into effect December 16, 2024. Here is what the rollout looks like through 2028:
| Period | What Happens |
|---|---|
| Dec 2024 - Dec 2025 (Phase 1) | CMMC requirements appear in select DoD solicitations. Self-assessment permitted with senior official affirmation for Level 2 contracts where DoD grants exception. C3PAO assessments for highest-priority programs. |
| Dec 2025 - Dec 2026 (Phase 2) | C3PAO assessments required for all Level 2 programs (exceptions eliminated for most CUI contracts). DCMA begins Level 3 government assessments for qualifying programs. |
| 2027 - 2028 (Phases 3-4) | Full implementation. All DoD contracts that involve FCI or CUI will include CMMC requirements. No new exceptions. Renewal cycle begins for contractors who were assessed in Phase 1-2. |
Most contractors pursuing new DoD contracts in 2026 should treat CMMC Level 2 with C3PAO assessment as the operative requirement. The exceptions are narrowing. Starting preparation early matters because the path from gap assessment to C3PAO-ready typically takes 6 to 18 months depending on the starting security posture and the complexity of your CUI environment.
Typical Timeline: Gap to Certified
Every engagement is different, but the following represents a common trajectory for a small to mid-size defense contractor with 25-250 employees:
- Month 1-2: Gap assessment and scoping. Identify current vs. required state across all 110 practices. Document the CUI boundary. Calculate the SPRS score delta.
- Month 2-6: Remediation. Implement missing controls. Priority order is typically: MFA, FIPS encryption, audit logging, access control policies, configuration management, incident response plan, and SSP completion.
- Month 6-10: Documentation and evidence collection. Complete the System Security Plan. Build the POA&M for residual gaps. Create the required policy documentation set across all 14 domains. Organize evidence artifacts.
- Month 10-12: Pre-assessment readiness review. A mock C3PAO assessment conducted by the RPO to identify any remaining gaps before the official assessment.
- Month 12-18: C3PAO assessment and certification. Official assessment with the C3PAO. Address any findings. Receive conditional CMMC status if applicable. Achieve full certification upon POA&M closure.
7. POA&M Rules and Conditional CMMC Status
A Plan of Action and Milestones (POA&M) is a document that identifies security weaknesses, the resources required to fix them, and the scheduled completion dates. CMMC 2.0 allows a limited use of POA&Ms at Level 2, which represents a significant change from earlier drafts of the rule where all 110 controls had to be fully implemented before assessment.
What POA&M Allows Under CMMC 2.0
- A contractor may receive conditional CMMC status (a time-limited certificate) if the C3PAO assessment finds deficiencies in a limited number of practices, provided none of the deficiencies involve specific high-priority practices.
- The POA&M closure period is 180 days from the date of the conditional certificate. All POA&M items must be closed and a closeout assessment completed within that window.
- Certain practices are excluded from POA&M eligibility, meaning they must be fully met at the time of the C3PAO assessment. These include multi-factor authentication requirements, FIPS-validated cryptography, and other high-priority controls specified by the DoD.
- A practice with a weighting of 5 points or more in the NIST 800-171 scoring methodology cannot be on the POA&M unless it meets specific conditions.
Strategic Implications
POA&M availability does not mean you can arrive at a C3PAO assessment with 40 open gaps and expect a conditional certificate. The rules are narrow. The best approach is to close as many gaps as possible before the assessment and use the POA&M only for residual, lower-weighted items where implementation requires longer technical timelines. An experienced CMMC practitioner will help you sequence remediation to maximize the likelihood of full certification at the first assessment attempt.
The DoD reserves the right to revoke conditional certificates if POA&M items are not closed within the 180-day window. An expired conditional certificate means the contractor can no longer perform on contracts requiring CMMC until a new assessment is completed.
8. What CMMC Compliance Costs
There is no single cost for CMMC compliance because the investment depends on how far away from compliant a contractor is today, how complex the CUI environment is, and how much internal IT capacity exists. That said, we can describe the cost components and typical ranges based on publicly available DoD cost estimates and common patterns in practice.
Cost Components
- Gap assessment and scoping: Typically conducted by an RPO. Includes review of existing controls, documentation, and CUI flow mapping. This defines the scope of remediation work ahead.
- Remediation: Technology purchases (MFA solutions, FIPS-compliant encryption, endpoint detection and response, SIEM, secure email), implementation labor, and configuration work. This is the largest variable cost and depends heavily on the starting state.
- Documentation and SSP authoring: Creating the System Security Plan, policies across all 14 domains, procedures, and the evidence artifact library. Labor-intensive but not hardware-dependent.
- C3PAO assessment fee: Paid directly to the C3PAO. The DoD's own cost estimates have ranged from approximately $30,000 to $100,000+ for a Level 2 assessment depending on organization size and scope complexity.
- Ongoing maintenance: Annual affirmation, continuous monitoring, vulnerability management, and preparation for the triennial reassessment. Typically an annual recurring cost.
The Cost of Not Complying
A contractor that cannot demonstrate CMMC Level 2 when required by the solicitation cannot bid on or perform on that contract. For companies with significant DoD revenue, the cost of non-compliance is contract loss. Additionally, false statements in DoD certifications can trigger False Claims Act liability, which carries civil penalties up to three times the value of the affected contracts.
The DoD's Regulatory Impact Analysis, published with the final rule, estimated average first-year compliance costs by company size. Small businesses in the 50-person range can expect first-year total costs (including C3PAO assessment) in the range of $100,000 to $300,000, with ongoing annual costs significantly lower. These are DoD estimates; actual costs vary widely.
9. Common CMMC Compliance Failures
After working with defense contractors on CMMC readiness since the program's early development, we see the same technical and organizational gaps consistently. Here are the most common compliance failures and what they mean in practice.
FIPS Validation Gaps in Encryption
Practice 3.13.11 requires FIPS-validated cryptographic modules. Commercial encryption tools that are NIST-approved algorithmically may still fail if the implementation is not FIPS 140-2 or 140-3 validated. BitLocker, for example, has a FIPS-compliant mode that must be explicitly enabled; default settings do not qualify. Assessors check module validation certificates, not just whether encryption is enabled.
MFA Not Applied to All Access Types
Practice 3.5.3 requires MFA for local access, network access, and remote access to privileged accounts. Many contractors implement MFA for remote desktop or VPN but leave local workstation login and privileged account elevation without a second factor. Assessors examine all access paths to CUI systems, not just external ones.
Unmanaged CUI Spread
Many contractors discover during scoping that CUI has spread beyond intended boundaries: into personal email, personal cloud storage, unmanaged employee devices, or collaboration tools not covered in the SSP. Every system that touches CUI is in scope. Reducing scope through CUI enclave strategies before assessment is the most cost-effective approach, but it requires careful data flow mapping first.
Flow-Down to Subcontractors Not Managed
DFARS 252.204-7021 requires prime contractors to flow down CMMC requirements to subcontractors handling CUI. Primes are responsible for verifying their subs' CMMC status before allowing CUI access. Many primes have not inventoried which subs touch CUI or confirmed those subs are on a path to certification. This creates contract performance risk for the prime.
Incident Reporting Window Missed
DFARS 252.204-7012 requires reporting cyber incidents affecting covered defense information to the DoD within 72 hours of discovery via the DIBNet portal. Many contractors have incident response plans that address internal notification but do not include the 72-hour external reporting requirement. Failure to report is itself a compliance violation separate from the incident.
SSP Describes Intent, Not Implementation
A System Security Plan should document how security controls are actually implemented in your specific environment, not simply restate the control requirement. Assessors frequently find SSPs that say "the organization uses multifactor authentication" without specifying which systems, which solution, and how it is configured. A well-written SSP is specific: named systems, specific product versions, configuration screenshots referenced, and named individuals with responsibilities.
Role-Based Training Not Distinguishable from Awareness Training
The AT domain requires both general security awareness training (AT-2) and role-based security training for individuals with security responsibilities (AT-3). Generic phishing simulation and compliance video platforms satisfy AT-2 but do not meet AT-3 for system administrators, security personnel, and others with elevated access or security roles. Assessors ask to see distinct training records for role-specific training.
10. Frequently Asked Questions
Do I need CMMC Level 2 or Level 1?
If your contracts involve Controlled Unclassified Information (CUI), you need Level 2. CUI is identified by the CUI Registry maintained by the National Archives; it includes categories like export-controlled technical data, proprietary military specifications, and certain acquisition-sensitive information. If your contracts involve only Federal Contract Information (FCI) with no CUI, Level 1 with annual self-assessment applies. When in doubt, look at the data labels and markings on what you receive from the prime or government and check DFARS clause 252.204-7021 in your contract.
What is the difference between an RPO and a C3PAO?
An RPO (Registered Practitioner Organization) provides advisory, consulting, gap assessment, and remediation services to prepare contractors for certification. An RPO cannot issue a CMMC certificate. A C3PAO (CMMC Third-Party Assessment Organization) conducts the official assessment and submits results to the government to generate the certificate. You typically work with an RPO to prepare, then engage a separate C3PAO for the official assessment. Petronella Technology Group is an RPO, not a C3PAO.
How long does it take to get CMMC Level 2 certified?
The path from first gap assessment to final C3PAO certification typically takes 6 to 18 months. The wide range reflects differences in starting security posture, complexity of the CUI environment, internal IT capacity, and speed of remediation decisions. Companies that have already been implementing NIST 800-171 under DFARS 7012 are generally closer to ready. Companies that have self-attested without implementing controls have more ground to cover.
Can I self-assess for CMMC Level 2?
Generally, no. CMMC 2.0 requires a C3PAO assessment for Level 2. The final rule does include limited exceptions where DoD may allow a senior official affirmation (self-assessment with annual affirmation) for certain Level 2 programs, but these exceptions apply to a narrow set of lower-sensitivity CUI programs. For most defense contractors bidding on contracts that specify CMMC Level 2 with C3PAO assessment, self-attestation is not an option.
What happens if I do not get CMMC certified in time?
If a solicitation requires CMMC Level 2 with C3PAO assessment and you do not hold a valid certificate, you cannot be awarded that contract. For existing contracts that add CMMC requirements at option exercise or modification, the contracting officer will work with you on a timeline, but continued performance may be conditioned on achieving certification. Starting the process early is the only reliable way to avoid this situation, given the 6-18 month typical timeline.
Does CMMC apply to cloud services we use?
Yes. If you store or process CUI in a cloud environment, that cloud service is in scope for your CMMC assessment. Cloud services that handle CUI must meet FedRAMP Moderate or equivalent requirements, and your SSP must document how the cloud service's controls map to the CMMC requirements. Many commercial cloud services do not meet these requirements. Using a non-compliant cloud service for CUI is one of the fastest ways to fail a C3PAO assessment.
What is the SPRS score and how is it calculated?
SPRS stands for Supplier Performance Risk System. The SPRS score for NIST 800-171 starts at 110 and decreases based on unimplemented controls, with each practice weighted from 1 to 5 points. A fully compliant organization scores 110. The DoD requires contractors subject to DFARS 252.204-7019 to post their current score to SPRS and update it whenever it changes. During C3PAO assessment preparation, improving your SPRS score is a useful way to track remediation progress. The final CMMC certificate is separate from the SPRS score, but the score reflects your actual implementation status.
Do subcontractors need their own CMMC certification?
Yes, when they handle CUI. DFARS 252.204-7024 requires prime contractors to include CMMC requirements in their subcontracts when subcontractors will handle CUI. Each subcontractor must independently achieve and maintain the required CMMC level. The prime contractor is responsible for verifying subcontractor CMMC status before granting CUI access. This is tracked in the CMMC SPRS database, which primes can query.
How often must CMMC certification be renewed?
Level 2 C3PAO assessments are valid for three years, with a required annual senior official affirmation that controls remain in place between assessments. The affirmation is not another C3PAO assessment but is a formal executive statement to the DoD. If a significant security incident occurs or the scope of the CUI environment changes materially, the DoD may require an earlier reassessment.
What is the relationship between CMMC and NIST 800-171?
CMMC Level 2 and NIST SP 800-171 Rev 2 share the same 110 security requirements. The difference is verification. NIST 800-171 under DFARS 252.204-7012 relied on self-attestation; a contractor could claim they met all 110 requirements with no independent verification. CMMC Level 2 requires a C3PAO to independently assess and verify each requirement. If you have been working toward NIST 800-171 compliance, you are working toward CMMC Level 2. The work is the same. The difference is someone independent now checks your work.
Explore CMMC and Compliance Resources
Everything a defense contractor needs across CMMC preparation, related frameworks, and adjacent compliance obligations.
Talk to a Registered Practitioner at Petronella Technology Group
Whether you are assessing your first DoD contract obligation or preparing for an upcoming C3PAO audit, our CMMC-RP certified team can tell you exactly where you stand and what it will take to get to certified. Call us at (919) 348-4912 or contact us online.