ASP.NET MVC Bad Practices: Optional Submodel With Required Property

Hi there,

Scan shows the issue with this scenario.

class Model {
    public string Name {get;set;}
    public int StudentId {get;set;}
    public SubModel Class {get;set;}
}

class SubModel {
    public string Title {get;set;}
    [Required]
    public int? Id {get;set;}
}

Submodel.Id is Required but it is also Nullable. Why should I mark Class property which is of type SubModel as [Required]? My business requirement does not say that Class is required. It appears to me that Fortify is not considering the fact that Id is nullable and simply shows an issue. Fortify team, can you guys please confirm as this is an issue in Fortify or suggest a way out. By the way, we are using 21.1.2 version.

Thanks,
Sai