Beyond Layers: Understanding Concentric Security, Defense in Depth, Balanced Protection, and Cradle-to-Grave Strategies

  We talk about concentric layers of security all the time in this industry. Concentric layers are one of the basic ways security professionals visualize layered protection. Whatever terminology an organization uses, the central idea is generally the same: do not rely on a single security measure to protect an asset. However, this concept goes much deeper than simply putting a fence around a building, installing cameras, placing an alarm on the door, and calling the facility secure. The real question is how those layers interact, what each layer is designed to accomplish, what happens when one layer fails, and where the organization is actually trying to stop the threat. Concentric security, defense in depth, balanced protection, and cradle-to-grave security can all be part of the same security strategy, but they are not the same strategy. Understanding the difference is important because each one looks at security from a different perspective.


 

  Concentric security is primarily concerned with where security layers are positioned in relation to the asset being protected. The outermost layer may begin beyond the property itself and include surrounding streets, neighboring properties, parking areas, lighting, landscaping, signage, natural surveillance, visibility, and other environmental conditions. Moving inward, additional layers may include fencing, gates, controlled entrances, building access, restricted areas, sensitive rooms, equipment, information systems, and ultimately the specific asset or function being protected. Generally, the closer an individual gets to the protected asset, the more restrictive and targeted the security environment becomes. That does not mean every organization needs multiple fences, multiple gates, and multiple locked doors. A layer can be physical, procedural, technological, environmental, administrative, or human. A professional security assessment should determine what type of layer is appropriate for the threat and the asset rather than simply adding another physical barrier.



  This distinction is important because a security layer is not necessarily a physical object. A fence can be a layer, but so can lighting. An access-control system can be a layer, but so can an employee identification procedure. A camera can be a layer, but so can a trained employee recognizing abnormal behavior. A security officer can be a layer, but so can a policy requiring authorization before access is granted. The important question is what function that layer performs. Does it deter? Detect? Verify? Delay? Deny? Alert? Provide information? Create time for a response? Limit the consequences after a breach? When security professionals begin evaluating layers by function instead of simply counting security devices, the quality of the security design changes significantly.


 

   This is where defense in depth becomes different from simply having concentric layers. Defense in depth is built on the assumption that individual security measures can fail. Cameras lose power. Alarms malfunction. Doors are propped open. Credentials are stolen. Employees make mistakes. Technology becomes unavailable. Communication systems fail. A determined adversary finds a vulnerability. A true defense-in-depth strategy is therefore designed so that the failure or defeat of one security measure does not automatically result in the failure of the entire security system. Each layer provides another opportunity to detect, deter, delay, interrupt, or respond to the threat. The objective is not simply to have more security. The objective is to have security that continues to provide protection when another security measure does not.



   Independence between systems is one of the most important nuances of defense in depth. An organization may have cameras, electronic access control, alarms, automated gates, and security officers and believe it has five separate layers of protection. But what happens if all of those systems depend upon the same electrical service, network infrastructure, communication system, administrator account, or control center? If one failure disables all of them, the organization may have multiple components but only one meaningful point of failure. Defense in depth therefore requires security professionals to look beyond the number of controls and examine their dependencies. If an adversary can defeat one system and automatically take several others with it, the organization may have layered security on paper without having true defensive depth.



   This is particularly important in today's physical security environment because technology is increasingly interconnected. A facility may have cameras, access control, alarms, intercoms, automated gates, environmental sensors, and other systems operating through shared infrastructure. Integration can make a security program more efficient, but integration can also create common points of failure. The more dependent the security architecture becomes on a single infrastructure, the more important redundancy and contingency planning become. Two cameras connected to the same network and electrical source may provide additional visibility, but they do not necessarily provide independent protection. Two different systems with different detection methods, different dependencies, and different response capabilities can create much greater defensive value.



    Another important function of layered security is creating time. Security professionals sometimes focus entirely on whether a barrier can stop an intruder, but stopping is only one possible function of a security measure. A barrier can create time for detection. Detection can create time for assessment. Assessment can create time for notification. Notification can create time for personnel or law enforcement to respond. Time can allow employees or occupants to move away from danger, allow systems to be shut down, or allow an organization to protect a critical asset. A layer does not necessarily have to permanently stop an adversary to be valuable. If it creates enough time for another layer to detect, assess, and respond, it may have accomplished exactly what it was designed to accomplish. This is one of the fundamental strengths of defense in depth.



   A correctional facility provides a useful example of this concept. An individual attempting to breach a secure correctional environment may encounter multiple physical boundaries, controlled gates, detection systems, observation points, personnel, controlled movement areas, internal barriers, locks, credentials, and monitored spaces. The important lesson is not simply the number of barriers. It is the distance, delay, detection, and response opportunities created between the outside environment and the protected population. A perimeter breach does not automatically mean access to the occupied facility. A person who defeats one access point may still have to overcome another. A failure of one technology does not necessarily eliminate the ability of personnel to observe or respond. The open area between security boundaries can itself become a security feature because it creates visibility and separation. The principle is straightforward: successfully penetrating one layer should not automatically provide successful penetration of the next.



   The same principle exists in information security. Endpoint protection, identity management, multifactor authentication, network segmentation, firewalls, encryption, monitoring, intrusion detection, logging, backups, incident response, and recovery capabilities can all contribute to defense in depth. If a malicious actor defeats one control, another should still have an opportunity to identify, contain, limit, or recover from the event. Again, the objective is not to accumulate technology simply because technology is available. If every security function depends upon the same compromised identity system, network, administrator account, or infrastructure, the organization may have more technology without substantially increasing its resilience. Layering without independence can create the appearance of defense in depth without the substance of it.



   Balanced protection is another concept that is often confused with defense in depth. The basic idea behind balanced protection is that meaningful security capability should be distributed throughout the system rather than concentrated exclusively around the final asset. Consider a facility with extremely strong security around an executive office but weak controls at the property boundary, employee entrance, loading dock, parking area, or service entrance. The organization may have a highly protected core while leaving the pathways to that core relatively exposed. A balanced approach asks whether there are meaningful opportunities for detection, deterrence, delay, or response across the pathways an adversary could reasonably use. This does not mean every layer needs identical security. Balanced does not mean equal. It means the protection is appropriately distributed according to the risk.



   This is where I would challenge the idea that every layer should have the same stopping power. It sounds attractive to say that the perimeter should be just as strong as the inner core, but that is not necessarily good risk management. Security resources are not unlimited, and not every location carries the same consequence if compromised. A parking area may require lighting, visibility, cameras, emergency communication, and appropriate patrols. A restricted server room may require substantially more restrictive access. A high-value storage area may require another level of protection. The professional objective is not to make every layer identical. The objective is to understand what each layer needs to accomplish and allocate resources according to probability, impact, vulnerability, consequence, operational requirements, and available resources.



   For a small business, defense in depth may be the most practical approach because resources are limited and the organization may need to concentrate its strongest protection around its most critical assets. A locked exterior door, monitored alarm, controlled interior office, separate safe, appropriate camera coverage, employee procedures, and a response plan can create several layers without requiring the organization to build a fortress. The important question is whether each measure contributes something different to the overall system. A business does not necessarily need the most expensive security technology available. It needs the right combination of measures that address its actual risks.



   Cradle-to-grave security introduces an entirely different perspective. Instead of asking only where the physical security layers are located, the professional follows the asset, activity, information, process, or operation throughout its entire lifecycle. Where does the asset originate? Who creates it? Who handles it? Where is it stored? Who has access? How is it transported? Who receives it? Where does it go afterward? How is it maintained? What happens when it is returned, replaced, retired, or destroyed? This approach is particularly important for sensitive information, high-value equipment, pharmaceuticals, intellectual property, financial information, supply chains, controlled materials, and other assets that move through multiple environments. The security problem does not necessarily end when an asset leaves the building. In many cases, that is where another risk begins.



   Consider sensitive information. It may be created on a corporate system, accessed by an employee, transmitted electronically, downloaded to another device, shared with a vendor, stored in a cloud environment, backed up, archived, and eventually destroyed. The physical office may have excellent security, but that does not mean the information is secure throughout its lifecycle. The same principle applies to physical assets. A product may be manufactured securely, transported through multiple carriers, stored in a warehouse, delivered to another organization, returned, repaired, resold, or destroyed. Each transition creates another opportunity for loss, theft, manipulation, substitution, or unauthorized access. Cradle-to-grave thinking forces the security professional to follow the asset rather than simply protect the building.



   The four concepts can therefore work together rather than compete with each other. Concentric layers help define where protection exists in relation to the asset. Defense in depth helps ensure that the failure of one layer does not automatically defeat the system. Balanced protection helps identify whether security is appropriately distributed across the pathways an adversary could use. Cradle-to-grave thinking extends the analysis beyond the physical facility and across the entire lifecycle of the asset, process, information, or operation. These are different perspectives applied to the same fundamental questions: Where can the threat enter? What can it exploit? What can detect it? What can slow it? What can stop it? What happens if it gets through? What happens afterward?



   This is also where security professionals need to stop thinking of the perimeter as the beginning of the security problem. The threat may begin much earlier. It may begin with information gathering, an employee posting sensitive information online, a vendor relationship, an unsecured delivery process, a compromised credential, predictable schedules, poor environmental design, or another condition that creates opportunity. By the time someone reaches the fence, the security professional may already be several steps behind. The perimeter is a location. It is not necessarily the beginning of the threat.



   The same thinking applies after the incident. A complete security strategy should consider what happens when prevention fails. If an adversary gets through the perimeter, what happens next? If they enter the building, what happens next? If they reach the protected asset, what happens next? If the asset is stolen or damaged, what happens next? If information is compromised, what happens next? If operations are interrupted, what happens next? Security begins connecting directly with enterprise risk management and business continuity at this point. Prevention is important, but an organization that has no ability to respond, continue operating, recover, and learn from the event has only addressed part of the risk.



   At Weedman & Co., we do not view layered security as simply adding another security measure every time a vulnerability is identified. The objective is to understand how the pieces interact. A camera that detects an event but does not generate a response may have limited practical value. An alarm that nobody monitors may create little protection. Access control that employees routinely bypass because it interferes with operations may exist on paper while failing in practice. A highly secure interior with an uncontrolled pathway leading directly to it may create a false sense of protection. Security has to function as a system, and that system has to account for people, technology, environment, procedures, behavior, operations, response, and recovery.



    This is also where our PACT approach provides another way to examine the problem. A security professional should not look only at whether a barrier exists. We need to understand the relationship between desire, ability, opportunity, environmental conditions, behavior, and the organization's capacity to respond. The goal is not to predict exactly what an offender will do. The goal is to understand the conditions that make an undesirable outcome more or less difficult to accomplish. That distinction matters because effective security is not simply about reacting to incidents. It is about understanding how the environment and the organization influence opportunity before the incident occurs.



   There is no universal security architecture. A small business, school, hospital, manufacturing facility, financial institution, residential community, critical infrastructure site, and government facility will not have the same risk profile or the same resources. That is why simply copying another organization's security program rarely works. The security professional's responsibility is to understand the risk, identify the critical assets, understand how those assets are exposed, determine where layers are necessary, establish appropriate independence between critical controls, create detection and response opportunities, and consider what happens when prevention fails.



   Concentric layers tell us where protection exists. Defense in depth tells us what happens when a layer fails. Balanced protection asks whether security is appropriately distributed across the system. Cradle-to-grave thinking follows the risk across the entire lifecycle. Understanding the distinction between these concepts allows security professionals to build more deliberate programs instead of simply accumulating security measures.



   Good security is not about making something impossible to penetrate. In many environments, that is unrealistic. It is about making the path to harm progressively more difficult, more visible, more time-consuming, and more likely to trigger an effective response while limiting the consequences if prevention ultimately fails. That is the difference between installing security and engineering security.




Reference concept: Carpency, F. (2008), "Systems Design and Engineering," Security Architecture & Engineering – Part 2.





About The Author:


Joseph Weedman, B.A., FCP, SRMP-C is the Founder & CEO of Weedman & Co., with more than two decades of hands-on experience building and operating businesses across security, protective services, investigations, emergency response, and risk management. He holds a Bachelor of Arts in Security Management, is a Florida Certified CPTED Practitioner (FCP), and holds the SRMP-C professional designation. His background spans physical security, information security, school and campus security, industrial espionage, risk management, business operations, and crisis response. As an operator, business owner, and risk professional, Mr. Weedman brings practical field experience to Enterprise Risk Management (ERM), ESRM, operational risk, resilience, compliance, supply-chain risk, and business continuity. His work today focuses on connecting security, operations, compliance, resilience, and enterprise risk management to help organizations better understand and manage the risks that affect their business.

Understanding Risk Assessment and Risk Analysis

By site-qCMZqg • October 4, 2026
Risk assessment and risk analysis are terms often used interchangeably, but they are not the same thing. Both are fundamental to effective risk management, yet each serves a different purpose. A risk assessment establishes an understanding of an organization's exposure. Risk analysis goes deeper, examining why that exposure exists, what could cause an event, how likely it may be, what the consequences could be, and how existing safeguards influence the outcome. The distinction is important because collecting information about risk is not the same as understanding risk. Risk Assessment: Identifying the Exposure A risk assessment begins with understanding the environment being evaluated. What are the organization's critical assets? What operations are essential? Who has access? What threats exist? What vulnerabilities are present? What safeguards are already in place? What dependencies could create additional exposure? The purpose is to establish a meaningful picture of the organization's risk environment and identify conditions that require attention. A professional risk assessment should do more than create a list of deficiencies. A missing camera, inadequate lighting, unsecured door, outdated policy, single-source vendor, or lack of emergency planning may all be observations, but an observation alone does not establish the significance of the risk. The assessment establishes what is present, what is absent, and what conditions deserve further examination. Risk Analysis: Understanding What the Exposure Means Risk analysis takes the identified exposures and examines them more deeply. Why does the vulnerability exist? What conditions make an event more or less likely? What would happen if the event occurred? How quickly would the organization recognize it? What would happen after detection? What resources would be required to respond? What operations could be interrupted? What dependencies could increase the consequences? This is where professional judgment becomes particularly important. Risk analysis is not simply assigning a number to a spreadsheet. It is interpreting the available information and understanding how the individual pieces interact. A useful distinction is simple: risk assessment identifies and evaluates the exposure; risk analysis interprets the exposure and examines its potential consequences. A Finding Is Not the Same as a Risk Consider a parking area with inadequate lighting. The assessment may identify the lighting deficiency. The analysis asks what that deficiency actually means. Is the area used after dark? Who uses it? Does the lack of lighting create concealment? Does it interfere with surveillance? Is there a history of incidents? Are employees required to walk through the area? Are there other security measures that compensate for the deficiency? Does the condition create a meaningful opportunity for crime, injury, or another loss? The lighting condition is the observation. Understanding how that condition affects the organization is the analysis. This distinction is one of the reasons experienced risk professionals cannot rely entirely on checklists. A checklist can identify conditions. It cannot always determine their significance. Data Does Not Make the Decision Modern risk professionals have access to more information than ever before. Crime statistics, incident histories, insurance losses, environmental information, operational metrics, surveillance records, financial information, and other data can all contribute to a risk assessment. But data should inform professional judgment, not replace it. Data can be incomplete, outdated, improperly collected, manipulated, misunderstood, or disconnected from the specific environment being evaluated. A crime statistic for a geographic area does not automatically determine the risk at a particular property. A low number of historical incidents does not necessarily mean the environment has low exposure. Likewise, a high incident rate does not automatically tell a professional what intervention will be most effective. The professional's responsibility is to determine what the information actually means in context. This is where risk assessment becomes more than data collection. The ability to see the environment, understand the information, recognize its limitations, and interpret it against probability, impact, vulnerability, and consequence is what turns information into usable risk intelligence. Probability, Impact, and Vulnerability Probability and impact are two of the most commonly discussed components of risk, but they should not be viewed in isolation. A relatively unlikely event can still deserve significant attention if the consequences would be severe. Conversely, a frequent event may require a different response when its consequences are limited and manageable. Vulnerability adds another dimension. Two organizations can face the same threat but have completely different levels of risk because their environments, operations, safeguards, personnel, resources, and response capabilities are different. A facility with strong access management, effective surveillance, trained personnel, appropriate lighting, established emergency procedures, and reliable communications may be substantially more resilient than a similar facility without those capabilities. The question therefore should not simply be, "What is the threat?" It should also be, "How vulnerable are we to it, and what happens if our existing safeguards fail?" Existing Security Measures Must Be Evaluated for Function One of the most common weaknesses in risk assessments is treating the presence of a security measure as proof that the risk has been addressed. A camera is not automatically effective security because it exists. An alarm is not automatically protective because it is installed. A policy is not automatically effective because it is written. A security officer does not automatically reduce risk simply because someone is standing at a post. The professional must examine how the measure actually functions. Does the camera provide meaningful coverage? Can footage be retrieved when needed? Is the alarm monitored? Who responds when it activates? Is the policy understood and followed? Does the security officer have the training, authority, equipment, and procedures necessary to perform the assigned function? The difference between security presence and security performance is an important part of professional risk analysis. Quantitative and Qualitative Risk Analysis Quantitative analysis uses numerical information to help evaluate risk. Financial loss estimates, incident frequency, downtime, replacement costs, probability calculations, and other measurable variables can be useful when reliable information exists. More sophisticated techniques can also be used when the risk and available data justify them. However, numerical precision should not be confused with certainty. A calculation can produce a very precise number while still being based on uncertain assumptions. Qualitative analysis relies more heavily on professional judgment, observations, interviews, experience, scenario analysis, and environmental context. This can be particularly valuable when reliable numerical data is limited or when the risk involves complex human, operational, or environmental factors that cannot easily be reduced to a single number. Neither approach should automatically be considered superior. The appropriate approach depends on the risk, the quality of the available information, and the decision that needs to be made. Risk Matrices Are Tools, Not Answers Risk matrices can be useful for organizing information and communicating priorities. They provide a common framework for considering probability and impact and can help organizations determine where additional attention may be warranted. But the matrix itself does not perform the analysis. A risk labeled "high," "medium," or "low" should have reasoning behind that classification. Two organizations may reasonably classify the same condition differently because their assets, operations, vulnerabilities, consequences, and risk tolerances are different. The value is not the color on the matrix. The value is the professional reasoning that produced it. Residual Risk Is Part of the Decision Risk rarely disappears completely. Even after safeguards are implemented, some level of exposure usually remains. That remaining exposure is residual risk. A mature risk assessment should therefore identify not only the original exposure, but also what happens after mitigation is applied. What has been reduced? What remains? What has changed? What risk is the organization still accepting? This is especially important for executives and decision-makers. They need to understand not only what has been corrected, but what remains and why the organization has decided to live with it. Risk management is not necessarily about eliminating every possible risk. In many environments, that would be impossible, operationally impractical, or financially unreasonable. The objective is to make informed decisions about the risks an organization chooses to address, transfer, mitigate, or retain. From Assessment to Risk Management The ultimate purpose of risk assessment and risk analysis is not to produce a report. It is to improve decision-making. The findings should help determine whether additional resources are justified, whether an existing safeguard should be changed, whether an operation should be redesigned, whether a vulnerability should be accepted, whether additional protection is warranted, or whether a portion of the financial exposure should be transferred through insurance or another mechanism. This is where assessment and analysis become part of a larger enterprise risk-management process. The assessment establishes the environment. The analysis provides meaning and context. Risk treatment determines what should be done. Monitoring and reassessment determine whether those decisions continue to be appropriate as conditions change. The Weedman & Co. Perspective A strong assessment identifies the environment and the exposure. A strong analysis explains why the exposure matters, what conditions contribute to it, how existing safeguards affect it, what the potential consequences are, and what options are available. The professional's job is not simply to collect data and assign a score. It is to see the environment, understand the information, interpret it within the context of the organization, evaluate probability and impact, understand vulnerability, and determine what the risk actually means. That requires experience, critical thinking, technical knowledge, and professional judgment. Risk management is not about predicting the future with perfect accuracy. It is about making better decisions with the information available while recognizing what is known, what is uncertain, and what could happen if the assumptions are wrong. About The Author: Joseph Weedman, B.A., FCP, SRMP-C is the Founder & CEO of Weedman & Co., with more than two decades of hands-on experience building and operating businesses across security, protective services, investigations, emergency response, and risk management. He holds a Bachelor of Arts in Security Management, is a Florida Certified CPTED Practitioner (FCP), and holds the SRMP-C professional designation. His background spans physical security, information security, school and campus security, industrial espionage, risk management, business operations, and crisis response. As an operator, business owner, and risk professional, Mr. Weedman brings practical field experience to Enterprise Risk Management (ERM), ESRM, operational risk, resilience, compliance, supply-chain risk, and business continuity. His work today focuses on connecting security, operations, compliance, resilience, and enterprise risk management to help organizations better understand and manage the risks that affect their business.

The PACT Model: A New Era of Crime Prevention Through Integrated Risk Analysis

By site-qCMZqg • July 10, 2024
Weedman & Co.’s Proactive Analysis for Crime and Threats (P.A.C.T)

Why a Thorough CPTED Assessment Matters Under Florida Statute 768.0706

By site-qCMZqg • June 10, 2024
Florida Statute 768.0706 changed the conversation surrounding security assessments for qualifying multifamily residential properties. The statute establishes a presumption against liability in connection with certain criminal acts committed by third parties when the owner or principal operator substantially implements specified security measures and satisfies the statute's other requirements. One of those requirements is particularly important to the security profession: the property must have a Crime Prevention Through Environmental Design, or CPTED, assessment that is no more than three years old and that is performed by a law enforcement agency or a Florida CPTED Practitioner designated by the Florida Crime Prevention Training Institute of the Department of Legal Affairs. The owner or principal operator must also remain in substantial compliance with that assessment. That distinction matters because an assessment is not simply another document that gets placed in a property management file. When security documentation may later become relevant to a liability claim, the quality of the assessment, the qualifications of the person conducting it, the conditions documented during the assessment, and what the property does with the findings all become important. A security assessment should not merely state that a property has cameras, lighting, locks, gates, or access controls. It should establish what was actually observed, what was evaluated, what conditions existed at the time of the assessment, what deficiencies were identified, and what corrective actions may be necessary. The difference between checking a box and conducting a defensible assessment is substantial. Florida's statute is also more specific than the general concept of conducting a "security assessment." Section 768.0706 applies to a defined category of multifamily residential property: a residential building or group of residential buildings such as apartments, townhouses, or condominiums consisting of at least five dwelling units on a particular parcel. The statute then identifies specific security measures, including entry and exit camera systems that record and maintain retrievable footage for at least 30 days, specified parking-lot lighting, lighting in walkways and common areas, at least a one-inch deadbolt on each dwelling-unit door, locking devices on specified windows and doors, locked gates with key or fob access around pool areas, and peepholes or door viewers where applicable. The important lesson for security professionals is that the statute should not be treated as a checklist that automatically creates protection once someone signs an assessment. The statutory language uses the term “substantially implements,” and the owner or principal operator carries the burden of demonstrating substantial implementation of the specified security measures. The assessment is therefore part of a larger compliance picture. The professional needs to understand what the statute requires, what the property actually has, whether those measures are functioning as intended, whether the physical environment supports the intended security outcome, and whether the property remains substantially compliant over time. This is where CPTED becomes particularly important. CPTED is not simply an evaluation of whether a property has enough lights and cameras. The broader purpose of CPTED is to examine how the physical environment influences behavior, visibility, access, territorial definition, activity, and opportunity. A property can technically possess the required security devices while still presenting environmental conditions that create unnecessary opportunities for crime. A camera may be installed but positioned poorly. A light fixture may be operational but fail to illuminate the area where visibility is actually needed. Landscaping may obscure sightlines. A gate may exist but remain routinely unsecured. An access-control system may be installed but undermined by operational practices. A security assessment should therefore examine the relationship between the security measure and the environment in which that measure is expected to function. This is one of the biggest differences between a professional CPTED assessment and a basic property walkthrough. A walkthrough may identify what is present. A meaningful assessment asks whether what is present is actually accomplishing its intended purpose. That requires observation, verification, documentation, and professional judgment. It also requires the assessor to understand that security conditions are not static. Properties change. Tenants change. Employees change. Landscaping grows. Lighting fails. Cameras are repositioned. Gates are damaged. Access procedures evolve. Construction alters sightlines. Parking patterns change. New amenities are added. A property that was appropriately assessed three years ago may not present the same security environment today. The three-year assessment requirement therefore should not be misunderstood as meaning that a property only needs to think about security once every three years. The statute establishes that the CPTED assessment must be no more than three years old, while also requiring the owner or principal operator to remain in substantial compliance with the assessment. That creates an ongoing responsibility rather than a one-time paperwork exercise. A property manager who receives an assessment identifying a deficiency cannot reasonably treat the assessment as complete simply because the document has been filed. The more important question becomes what happened after the assessment. Was the deficiency corrected? Was the correction documented? Did the physical condition change? Did the corrective action actually resolve the identified issue? Documentation becomes particularly important here. A defensible assessment should allow another professional to understand what was examined and what was observed without relying entirely on the assessor's memory. Photographs, measurements where appropriate, descriptions of physical conditions, identification of access points, observations regarding lighting and visibility, documentation of security equipment, and explanations of identified deficiencies can all contribute to a stronger record. Documentation should describe the condition that actually existed rather than simply repeating what a property manager says should exist. There is a major difference between writing "security cameras are installed" and documenting where the cameras are located, what areas they cover, whether they are operational, whether footage is retrievable, and whether their placement supports the intended security function. This is particularly relevant to cameras because the statutory requirement is not merely the presence of a camera. For the specified entry and exit camera system, the statute addresses recording and maintaining retrievable footage for at least 30 days to assist in offender identification and apprehension. A camera that is physically mounted to a building but is not recording, cannot retrieve footage, does not cover the relevant entry or exit, or does not retain footage for the required period raises a very different compliance question than a properly functioning system. Lighting provides another useful example. Security professionals should be careful not to treat the existence of a light fixture as equivalent to adequate lighting. Section 768.0706 establishes a specific lighting requirement for parking lots and also addresses lighting in walkways, laundry rooms, common areas, and porches. A professional assessment should therefore distinguish between the presence of lighting equipment and the actual lighting condition of the environment. Dark areas, obstructed fixtures, failed lamps, poorly positioned lighting, or environmental conditions that create shadows can change the security characteristics of a property even when the property technically has lighting installed. The same principle applies to doors, windows, gates, and other access points. Security is not established merely because a lock exists. The assessor should consider whether the required locking device exists, whether it is functioning, whether the door or window can actually be secured, whether the access point is being routinely defeated by operational practices, and whether the physical environment creates another path around the intended security measure. This is where experienced assessment becomes more valuable than a simple inventory. The objective is not merely to identify security equipment. It is to understand whether the security architecture works as intended. The statute also addresses employee training. By January 1, 2025, qualifying owners or principal operators were required to provide proper crime-deterrence and safety training to current employees, and employees hired after that date must receive the training within 60 days of hire. The statute defines that training in relation to the security principles, devices, measures, and standards identified in the statute and requires the training to be reviewed at least every three years and updated as necessary. The owner or operator may request that the law enforcement agency or CPTED Practitioner conducting the assessment review the training curriculum. That provision reinforces another important security principle: technology and physical measures are only part of the security system. Employees interact with the environment every day. They open and close gates, issue credentials, observe suspicious behavior, receive visitors, respond to alarms, report maintenance problems, and make decisions that can either support or undermine the security design. A property can invest heavily in physical security and still create vulnerabilities through poor employee practices. Training therefore should not be treated as an administrative requirement disconnected from the physical assessment. The people operating the property are part of the security environment. From a Weedman & Co. perspective, this is where the assessment needs to move beyond compliance and into risk management. The question should not simply be, "Do we have the required device?" The better question is, "What risk is this measure intended to address, and is it functioning in the environment in which it was installed?" That distinction is important because security is rarely effective when it is designed around individual products instead of the relationship between the threat, the environment, the asset, the people, and the consequences of failure. A professional CPTED assessment should therefore identify the conditions that influence opportunity. Where are people expected to walk? Where are vehicles entering and leaving? Where are the blind spots? Where do residents gather? Where can someone approach a building without being observed? Which doors are routinely used? Which gates are frequently left open? Where does landscaping obstruct visibility? Where are lighting deficiencies located? Where does pedestrian movement intersect with vehicle movement? Where does normal resident behavior create predictable patterns? These questions help transform a security assessment from an equipment inventory into an analysis of the environment. This is also why the qualifications of the assessor matter. Section 768.0706 specifically identifies who may perform the CPTED assessment for purposes of the statute: a law enforcement agency or a Florida CPTED Practitioner designated by the Florida Crime Prevention Training Institute of the Department of Legal Affairs. The statute does not simply say that any security consultant may conduct the required assessment. For a property seeking to rely on the statutory presumption, understanding the statutory qualification requirement is essential. The legal significance should also be described accurately. Section 768.0706 does not create blanket immunity for multifamily properties. It establishes a presumption against liability when the statutory requirements are met, and the owner or principal operator bears the burden of demonstrating substantial implementation of the specified security measures. The statute also expressly states that it does not establish a private cause of action. Security professionals should therefore avoid promising property owners that an assessment will "prevent a lawsuit" or "eliminate liability." A professional assessment is not a legal guarantee. What it can do is provide documented evidence of the property's security condition and its efforts toward substantial compliance with the statutory framework. That distinction is especially important when attorneys become involved. In litigation, the question may not simply be whether an assessment exists. Questions can arise concerning when it was performed, who performed it, what was actually inspected, what conditions existed, whether the required security measures were implemented, whether deficiencies were identified, whether corrective actions were taken, and whether the property remained substantially compliant. The assessment therefore becomes part of a larger evidentiary record. The more accurately that record reflects the physical property and the actions taken by management, the more useful it can become to the organization and its legal and insurance professionals. This is where the concept of an Underwriting Defense Package or risk-engineering record can become valuable from an enterprise risk perspective. A property owner should not have to reconstruct its security history after an incident occurs. There should already be documentation showing what was assessed, what was found, what was corrected, what remained outstanding, who was responsible for corrective action, and when the condition was revisited. Security documentation becomes far more useful when it demonstrates a continuing process rather than a single inspection date. The same information can have value beyond litigation. Insurance professionals, risk managers, property managers, ownership groups, and corporate decision-makers increasingly need a better understanding of the conditions underlying a property's risk. A professional assessment can provide a common factual foundation for those conversations. It can identify conditions that require investment, distinguish operational deficiencies from physical deficiencies, and help management prioritize corrective action according to risk rather than simply reacting to whatever problem receives the most attention that week. The most important lesson is that a CPTED assessment should not be treated as a compliance document that is completed, signed, filed, and forgotten. It should be treated as a snapshot of the property's security environment and the beginning of a continuing process of verification and improvement. The assessment establishes what was observed. Management's actions afterward demonstrate what the organization did with that information. When those two pieces remain connected, the assessment becomes much more meaningful. Florida Statute 768.0706 gives qualifying multifamily property owners and operators a specific statutory framework for establishing a presumption against liability when the required security measures and assessment requirements are substantially implemented. But the strength of that position depends on more than possessing a document with "CPTED Assessment" written across the top. It depends on whether the property actually implements the applicable security measures, whether the assessment accurately reflects the property, whether deficiencies are addressed, and whether the organization can demonstrate what it did with the information it received. For security professionals, that should be the larger takeaway. An assessment is not valuable because it says a property is secure. It is valuable because it documents what was actually examined, identifies what was found, explains why it matters, and creates a defensible record of what should happen next. The professional's job is not to make a property appear secure on paper. It is to help the owner understand the actual security environment and make informed decisions about risk. At Weedman & Co., we believe that is where CPTED becomes more than a compliance exercise. It becomes part of a broader enterprise risk-management process that connects physical security, property operations, employee practices, liability exposure, insurance considerations, business continuity, and corrective action. Security was the foundation. Global ERM is where we are today. This article is intended for educational and professional discussion and is not legal advice. Florida Statute 768.0706 should be reviewed in its current form, and property owners should consult qualified legal counsel regarding the application of the statute to their specific circumstances. Current statutory reference: Florida Statute §768.0706, Multifamily residential property safety and security; presumption against liability. About The Author: Joseph Weedman, B.A., FCP, SRMP-C is the Founder & CEO of Weedman & Co., with more than two decades of hands-on experience building and operating businesses across security, protective services, investigations, emergency response, and risk management. He holds a Bachelor of Arts in Security Management, is a Florida Certified CPTED Practitioner (FCP), and holds the SRMP-C professional designation. His background spans physical security, information security, school and campus security, industrial espionage, risk management, business operations, and crisis response. As an operator, business owner, and risk professional, Mr. Weedman brings practical field experience to Enterprise Risk Management (ERM), ESRM, operational risk, resilience, compliance, supply-chain risk, and business continuity. His work today focuses on connecting security, operations, compliance, resilience, and enterprise risk management to help organizations better understand and manage the risks that affect their business.