iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Short answer: choose CSPM when your main problem is cloud misconfiguration, visibility, compliance, and posture remediation; choose CWPP when you need to secure workload behavior and vulnerabilities across virtual machines, containers, Kubernetes, or serverless; evaluate a CNAPP when you need those protections connected across cloud infrastructure, identities, development pipelines, and runtime operations. The labels overlap, and a CNAPP is not automatically a complete bundle. Confirm each product’s cloud coverage, workload support, depth of controls, integrations, deployment model, prioritization, and remediation workflow before buying.
What do CNAPP, CSPM and CWPP mean?
These terms describe related capability families rather than three universally separate products. Their practical difference is the security object each one emphasizes: cloud configuration and posture, deployed workloads, or a broader cloud-application protection program.
| Category | Primary focus | Examples of scope | What to validate |
|---|---|---|---|
| CSPM Cloud security posture management |
Finding, prioritizing and helping remediate configuration vulnerabilities and compliance issues. | Cloud and multicloud resource visibility, misconfiguration detection, risk prioritization and remediation. | Supported providers, accounts, regions, hybrid environments, policy depth and remediation workflow. |
| CWPP Cloud workload protection platform |
Protecting workload-level behavior and security controls. | Virtual machines, containers, Kubernetes workloads and serverless functions; hardening, vulnerability management, host segmentation, integrity monitoring and application allow lists. | Coverage for the actual workload estate, runtime signals, deployment method and operational overhead. |
| CNAPP Cloud-native application protection platform |
Aligning visibility and protections for deployed cloud applications across multiple security domains and lifecycle stages. | Often combines posture, workload, identity or entitlement, development-pipeline and related controls. | Which components are included, how deeply they work, and whether findings are correlated into actionable risks. |
What is CSPM?
CSPM continuously examines cloud environments for resources, insecure settings and compliance conditions. The UK National Cyber Security Centre groups CSPM functionality into four areas: resource visibility, misconfiguration detection, risk prioritisation and remediation. Its guidance is useful because it frames CSPM as an operating process, not merely a scanner. A tool that produces thousands of findings without helping teams decide what to fix first is only covering part of the problem. See the NCSC explanation of CSPM functionality.
Free tools Windows power users keep installed
One-click scans. No signup required.
What is CWPP?
CWPP protects the workloads that run applications. Those workloads can be virtual machines, containers, Kubernetes workloads and serverless functions. Controls may include system hardening, vulnerability management, host-based segmentation, system-integrity monitoring and application allow lists, as described by Microsoft’s CWPP overview and CISA’s cloud guidance. The relevant question is not whether a platform uses the CWPP label, but whether it can observe and protect every workload type you operate.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
What is CNAPP?
CNAPP is a broader platform approach intended to connect protections around cloud applications. CISA defines it as “Capabilities that help align the visibility and security protections for deployed cloud applications.” Depending on the product, that may include CSPM, CWPP, identity and entitlement management, development-pipeline checks, data-related controls and other functions. The CISA TIC 3.0 Cloud Use Case and the Microsoft CNAPP overview both emphasize that the category is about alignment, while individual product scope still needs verification.
Are CNAPP, CSPM and CWPP separate products?
No. CSPM and CWPP can be purchased as focused capabilities, and either can also appear inside a CNAPP platform. “CNAPP” does not define one mandatory feature list, so two products carrying that name may differ substantially in posture checks, workload depth, identity context, Kubernetes support or development integration.
Think of the labels as overlapping layers. CSPM asks whether cloud resources are configured safely. CWPP asks whether the workloads running on those resources are hardened, vulnerable or behaving suspiciously. CNAPP attempts to connect those answers with identities, code and deployment context so a team can investigate one risk across its lifecycle. A platform may deliver strong posture management but shallow runtime protection, or excellent workload controls without broad cloud-account visibility. Procurement must test the individual capabilities rather than accepting the category name as proof.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Which security gap does each category address?
Choose CSPM for configuration and posture exposure
CSPM is the natural starting point when teams cannot reliably answer basic inventory and configuration questions: which resources exist, whether they follow policy, which settings create exposure, and who owns the fix. It is also relevant when compliance evidence and repeatable remediation are major requirements. The NCSC’s four-part model—visibility, detection, prioritization and remediation—gives you a way to check whether a proposed tool supports the full workflow instead of only generating alerts.
Choose CWPP for workload vulnerabilities and runtime behavior
CWPP is aimed at the software and operating environments that execute workloads. It becomes important when you need hardening, vulnerability management, host-level segmentation, integrity monitoring, application allow lists or runtime telemetry. Confirm support for virtual machines, containers, Kubernetes and serverless independently; support for one does not establish support for the others.
Evaluate CNAPP when correlation and lifecycle coverage are the problem
CNAPP is worth evaluating when separate tools leave security and development teams with disconnected findings. The value proposition is a connected view that can relate a risky cloud configuration to an exposed workload, an identity entitlement or a development-stage issue. That value depends on actual integrations and data depth, so ask for demonstrations using your cloud providers, deployment systems and workload types.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Do you need a CNAPP or just CSPM?
Use the following sequence to match the investment to a concrete gap instead of buying the broadest acronym.
- Document the current failure. Record whether incidents or audit findings originate in resource configuration, workload vulnerabilities, runtime behavior, identity permissions, development pipelines or several of these areas.
- Map the estate. List cloud providers, accounts, regions, hybrid or on-premises systems, virtual machines, containers, Kubernetes clusters and serverless functions. A product that cannot see a major part of this estate cannot provide complete coverage.
- Separate must-have controls from future scope. Mark the controls required on day one, such as misconfiguration detection or runtime monitoring, and those you may add later, such as pipeline checks or entitlement analysis.
- Test whether correlation changes decisions. If analysts repeatedly join findings manually across tools, a CNAPP’s unified context may reduce investigation effort. If your immediate need is a single posture inventory, a focused CSPM deployment may be simpler.
- Check ownership and workflow. Identify who receives findings, who approves exceptions and who performs remediation. A platform that cannot fit those handoffs will create alert volume without reducing risk.
- Compare total operating cost. Include licensing, agents or connectors, maintenance, integration work, training and alert management, not only the subscription quote.
This process can lead to a focused CSPM, a focused CWPP, several integrated capabilities or a CNAPP evaluation. The answer should follow the documented gap and estate, not the marketing breadth of a product category.
Does CWPP protect cloud workloads at runtime?
Runtime protection is a central CWPP concern, but the exact signals and controls differ by workload type and implementation. A CWPP may monitor workload behavior and provide controls such as system hardening, vulnerability management, host-based segmentation, system-integrity monitoring and application allow lists. Those functions are listed in CISA-aligned descriptions and Microsoft’s explanation of the category.
Ask vendors to show the control operating on each representative workload: a virtual machine, a container image and running container, a Kubernetes workload, and a serverless function if you use one. Also ask what happens when the workload is ephemeral, rebuilt frequently or managed through a hybrid environment. “Runtime protection” should be treated as a set of tested controls, not a blanket promise that every workload receives identical visibility.
What should a CNAPP actually include?
There is no universal CNAPP bill of materials. Use this checklist to turn a broad label into testable requirements.
| Capability area | Questions to ask |
|---|---|
| Posture management | Does it discover resources, detect misconfigurations, prioritize risks and support remediation across every required cloud account and region? |
| Workload protection | Are your virtual machines, containers, Kubernetes workloads and serverless functions supported, and which hardening, vulnerability and runtime controls are included? |
| Identity and entitlement context | Can the platform show how identities and permissions contribute to a cloud-application risk, and is that capability included or separately licensed? |
| Development and supply-chain checks | Can developers receive findings in existing development or CI/CD workflows, and at what stages are checks performed? |
| Data and application context | Does the product add data or application context that helps distinguish an exploitable path from an isolated configuration issue? |
| Kubernetes coverage | Does protection extend to clusters, workloads and deployment workflows you actually use, rather than only to the underlying cloud account? |
| Risk correlation | Does it connect related findings into an actionable risk with an owner, priority and remediation path? |
Ask which items are native, which require add-ons and which are integrations with another product. Request documentation for data retention, supported versions and deployment prerequisites before treating a checkbox as delivered functionality.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
How should you compare cloud security platforms?
Compare products on operating outcomes, not feature-count slides. Microsoft identifies hybrid and multicloud support, DevSecOps integration, Kubernetes protection, supply-chain security, agent-based versus agentless trade-offs and total cost of ownership as useful evaluation factors. Use those factors as a buyer’s checklist, then validate each claim in your environment.
| Decision axis | Evaluation questions |
|---|---|
| Coverage | Which cloud providers, accounts, regions and hybrid environments are supported? Are there limits by account, resource or geography? |
| Workloads | Does protection cover the team’s virtual machines, containers, Kubernetes clusters and serverless functions? |
| Capability depth | Are configuration checks, vulnerability management, runtime signals, identity context and development scanning included at the depth required? |
| Workflow fit | Can developers and security teams consume findings in existing CI/CD and cloud-operations workflows? |
| Deployment model | What visibility, permissions, agents, connectors and maintenance obligations come with agent-based and agentless collection? |
| Prioritization and remediation | Can the platform rank risks in context, assign ownership and guide an actionable fix or exception? |
| Cost and overhead | What are the licensing, integration, maintenance, training and alert-management costs over the intended term? |
What are the trade-offs between agent-based and agentless collection?
Agent-based collection can provide workload-level telemetry and enforcement, but it introduces deployment, updating and performance-management responsibilities. Agentless collection can reduce installation work and may be easier to roll out across accounts, yet its visibility and response options depend on the provider interfaces and data it can access. Neither model is automatically superior.
Ask for a workload-by-workload matrix: what is visible without an agent, what requires an agent, which controls are preventive or detective, what permissions are required, and how coverage changes for short-lived containers or serverless functions. Include operational teams in the decision because the collection model affects maintenance, change management and incident response.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How do these tools fit development and cloud operations?
Security findings only reduce risk when they reach the team able to fix them. During evaluation, trace one finding from discovery to closure:
- Creation: identify whether the issue originates in infrastructure configuration, source or build artifacts, an identity relationship, a workload vulnerability or runtime behavior.
- Context: confirm that the platform shows the affected resource, workload, account, identity and deployment relationship when those data are available.
- Routing: verify that ownership can be assigned to the correct development, platform or security team without creating duplicate tickets.
- Decision: test severity, exploitability or exposure context and the process for documenting an accepted exception.
- Remediation: check whether the platform provides a concrete fix path, links to the responsible workflow or supports a repeatable change process.
- Verification: confirm that a corrected resource or rebuilt workload clears the finding and that unresolved risk remains visible.
A CNAPP may make this chain easier by correlating lifecycle data, but integration quality is product-specific. A narrowly scoped CSPM or CWPP can still fit well if it delivers clear ownership and reliable handoffs.
How should risks be prioritized and remediated?
Prioritization is more than sorting by scanner severity. The NCSC’s CSPM model places risk prioritisation between detection and remediation, which means the platform should help teams decide what matters first and why. Ask whether priority reflects exposure, affected assets, workload importance, identity relationships and the ability to exploit a path, or whether every alert receives essentially the same treatment.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Remediation support should be equally concrete. Determine whether the product can assign an owner, supply a recommended configuration change, open or update an existing workflow and record exceptions. Test a complete fix during a proof of concept; a dashboard screenshot does not prove that the operational loop works.
Recommended Free Tools
What cloud and workload coverage must be verified?
- Providers and accounts: list every provider, subscription or account, organizational folder and region that needs monitoring.
- Hybrid assets: identify on-premises or private-cloud workloads that must appear beside public-cloud resources.
- Compute types: confirm separate support statements for virtual machines, containers, Kubernetes and serverless.
- Lifecycle states: test newly created, rebuilt, paused and deleted resources so inventory does not depend on long-lived assets.
- Permissions: document the access required for discovery, scanning, enforcement and remediation.
- Regional and edition limits: ask whether capabilities vary by geography, cloud edition or workload size.
Coverage claims should be written into the evaluation record with the exact account types and workload versions tested. “Multicloud” is not a substitute for naming the providers and services your organization depends on.
How do cost and operational overhead change the decision?
Cloud security cost includes more than a license. Count deployment and connector work, agent maintenance, policy tuning, integration with development and ticketing systems, analyst time spent triaging alerts, and the effort required to maintain exceptions. A broad platform can reduce the number of consoles, but it can also introduce modules, data-ingestion charges or administrative complexity that are not obvious in a feature list.
Build a three-part estimate: the subscription or license structure, the people and infrastructure needed to operate it, and the cost of unresolved or duplicated findings. Compare a focused capability with a broader platform using the same cloud accounts and workload set. This makes the trade-off visible without assuming that consolidation is always cheaper.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What is a practical implementation plan?
- Inventory the estate. Record providers, accounts, regions, hybrid systems, workload types and ownership.
- Define control objectives. Separate posture, workload, identity, development and runtime requirements, and mark which are mandatory.
- Select a representative pilot. Include the most important cloud account, a typical virtual machine, a containerized service, a Kubernetes workload and a serverless function where applicable.
- Compare collection models. Document permissions, agents, connectors, visibility, enforcement and maintenance for each pilot workload.
- Exercise the workflow. Send findings to the teams that remediate them, test prioritization, record an exception and verify closure.
- Tune policy and ownership. Remove duplicate alerts, define escalation paths and agree on how accepted risk is documented.
- Plan expansion. Add remaining accounts and workload types only after the pilot demonstrates reliable visibility and remediation.
What mistakes commonly undermine a cloud security purchase?
- Buying the acronym: assuming every CNAPP includes the same posture, workload, identity and development functions.
- Ignoring workload diversity: treating virtual-machine coverage as proof of container, Kubernetes or serverless coverage.
- Measuring alerts instead of outcomes: celebrating finding volume without testing prioritization, ownership and closure.
- Leaving developers out: selecting controls that cannot appear in existing development and deployment workflows.
- Underestimating collection operations: overlooking permissions, agent updates, connector maintenance and hybrid-environment constraints.
- Skipping remediation tests: accepting a dashboard demonstration without proving that a real change clears the original risk.
- Comparing unlike scopes: evaluating one product on a single account and another across the entire estate, then treating the results as equivalent.
Which approach fits common environments?
| Environment or priority | Likely starting point | Reason to expand or combine |
|---|---|---|
| Single-cloud environment with inconsistent resource settings and audit pressure | CSPM | Add workload protection when vulnerability or runtime requirements are not covered by posture checks. |
| Container and Kubernetes estate with emphasis on hardening and runtime behavior | CWPP with verified Kubernetes coverage | Add posture and identity context when configuration and entitlement relationships affect prioritization. |
| Multicloud or hybrid estate with separate security and development workflows | CNAPP evaluation | Confirm that the platform’s individual CSPM and CWPP components are deep enough for the estate. |
| Organization that already operates effective focused tools | Integrate existing capabilities first | Consider CNAPP only if correlated context or consolidation solves a documented operational gap. |
These are decision patterns, not guarantees. Your provider mix, workload inventory, team ownership and required controls determine the appropriate combination.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhat questions should procurement ask?
- Which providers, accounts, regions and hybrid resources can you discover and protect?
- Which controls are included for virtual machines, containers, Kubernetes and serverless, and which require separate modules?
- What posture checks are available, how are they prioritized, and how is remediation tracked?
- Which identity, entitlement, data and development-pipeline capabilities are native?
- What is visible with agentless collection, and what requires agents or additional permissions?
- How are findings correlated, deduplicated, assigned and closed?
- Which integrations support our CI/CD, ticketing and cloud-operations processes?
- How do licensing, ingestion, agents, connectors, maintenance and analyst time affect total cost of ownership?
- Can you demonstrate a complete remediation on our representative workloads?
- What coverage or functionality changes by cloud region, edition, workload version or deployment model?
How can you make the decision defensibly?
Keep a written capability matrix tied to your actual estate. For every required control, record the product component, supported workload, data source, deployment requirement, owner, remediation path and evidence from the pilot. This prevents a broad CNAPP label from hiding a missing function and prevents a focused tool from being dismissed simply because it does not use the broader name.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
The defensible choice is the combination that closes your highest-priority gap with acceptable operational effort. CSPM, CWPP and CNAPP are useful shorthand, but the cloud providers, workloads, integrations and remediation process you can verify are what determine security coverage.
Frequently Asked Questions
Can a small security team start with CSPM and add CWPP later?
Yes. CSPM and CWPP are separate capability areas, so an organization can address configuration visibility first and add workload controls when its estate or threat model requires them. Document the future workload requirements early so the initial architecture does not block agent, connector or workflow integration later.
Does every CNAPP include identity and entitlement management?
No. Identity or entitlement controls may be included, separately licensed or absent. Ask for the exact identity sources, permission analysis and correlation behavior rather than treating the CNAPP label as proof of coverage.
Are Kubernetes and serverless workloads covered by every CWPP?
No. CWPP scope varies by workload type and implementation. Request separate support statements and demonstrations for Kubernetes clusters, container workloads and serverless functions instead of inferring coverage from virtual-machine support.
What should a proof of concept test besides the dashboard?
Use representative accounts and workloads, compare agent-based and agentless visibility, route findings to real owners, perform a remediation and verify that the risk state changes. Also record required permissions, maintenance work and any gaps that appear in hybrid or short-lived workloads.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
